libfprint →
1:1.94.6-2 →
armhf → 2023-09-16 04:25:53
sbuild (Debian sbuild) 0.72.0 (25 Oct 2016) on mb-lxc-01
+==============================================================================+
| libfprint 1:1.94.6-2 (armhf) Sat, 16 Sep 2023 04:12:50 +0000 |
+==============================================================================+
Package: libfprint
Version: 1:1.94.6-2
Source Version: 1:1.94.6-2
Distribution: trixie-staging
Machine Architecture: armhf
Host Architecture: armhf
Build Architecture: armhf
I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/trixie-staging-armhf-sbuild-41cd2286-9212-4cec-8809-e0542a63639b' with '<<CHROOT>>'
+------------------------------------------------------------------------------+
| Update chroot |
+------------------------------------------------------------------------------+
Get:1 http://172.17.4.1/private trixie-staging InRelease [11.3 kB]
Get:2 http://172.17.4.1/private trixie-staging/main Sources [14.1 MB]
Get:3 http://172.17.4.1/private trixie-staging/main armhf Packages [14.6 MB]
Fetched 28.7 MB in 13s (2292 kB/s)
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
W: http://172.17.4.1/private/dists/trixie-staging/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
+------------------------------------------------------------------------------+
| Fetch source files |
+------------------------------------------------------------------------------+
Check APT
---------
Checking available source versions...
Download source files with APT
------------------------------
Reading package lists...
NOTICE: 'libfprint' packaging is maintained in the 'Git' version control system at:
https://salsa.debian.org/debian/libfprint.git
Please use:
git clone https://salsa.debian.org/debian/libfprint.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 9071 kB of source archives.
Get:1 http://172.17.4.1/private trixie-staging/main libfprint 1:1.94.6-2 (dsc) [2586 B]
Get:2 http://172.17.4.1/private trixie-staging/main libfprint 1:1.94.6-2 (tar) [9054 kB]
Get:3 http://172.17.4.1/private trixie-staging/main libfprint 1:1.94.6-2 (diff) [14.2 kB]
Fetched 9071 kB in 1s (6704 kB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 'build/libfprint-jSxESG/libfprint-1.94.6' with '<<PKGBUILDDIR>>'
I: NOTICE: Log filtering will replace 'build/libfprint-jSxESG' with '<<BUILDDIR>>'
+------------------------------------------------------------------------------+
| Install build-essential |
+------------------------------------------------------------------------------+
Setup apt archive
-----------------
Merged Build-Depends: build-essential, fakeroot
Filtered Build-Depends: build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive/sbuild-build-depends-core-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning: sbuild-build-depends-core-dummy
dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
gpg: keybox '/<<BUILDDIR>>/resolver-ZkoOF3/gpg/pubring.kbx' created
gpg: /<<BUILDDIR>>/resolver-ZkoOF3/gpg/trustdb.gpg: trustdb created
gpg: key 37145E60F90AF620: public key "Sbuild Signer (Sbuild Build Dependency Archive Key) <buildd-tools-devel@lists.alioth.debian.org>" imported
gpg: Total number processed: 1
gpg: imported: 1
gpg: key 37145E60F90AF620: "Sbuild Signer (Sbuild Build Dependency Archive Key) <buildd-tools-devel@lists.alioth.debian.org>" not changed
gpg: key 37145E60F90AF620: secret key imported
gpg: Total number processed: 1
gpg: unchanged: 1
gpg: secret keys read: 1
gpg: secret keys imported: 1
gpg: using "Sbuild Signer" as default secret key for signing
Ign:1 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ InRelease
Get:2 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ Release [957 B]
Get:3 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ Release.gpg [370 B]
Get:4 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ Sources [349 B]
Get:5 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ Packages [433 B]
Fetched 2109 B in 1s (3025 B/s)
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...
Install core build dependencies (apt-based resolver)
----------------------------------------------------
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
krb5-locales libpam-cap netbase sensible-utils sgml-base
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
Need to get 852 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ sbuild-build-depends-core-dummy 0.invalid.0 [852 B]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 852 B in 0s (47.9 kB/s)
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ... 11771 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy_0.invalid.0_armhf.deb ...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges
+------------------------------------------------------------------------------+
| Check architectures |
+------------------------------------------------------------------------------+
Arch check ok (armhf included in any all)
+------------------------------------------------------------------------------+
| Install package build dependencies |
+------------------------------------------------------------------------------+
Setup apt archive
-----------------
Merged Build-Depends: debhelper-compat (= 13), gobject-introspection, gtk-doc-tools, libcairo-dev, libgirepository1.0-dev, libglib2.0-dev, libgudev-1.0-dev, libgusb-dev, libnss3-dev, libpixman-1-dev, meson, python3, python3-cairo, python3-gi, umockdev
Filtered Build-Depends: debhelper-compat (= 13), gobject-introspection, gtk-doc-tools, libcairo-dev, libgirepository1.0-dev, libglib2.0-dev, libgudev-1.0-dev, libgusb-dev, libnss3-dev, libpixman-1-dev, meson, python3, python3-cairo, python3-gi, umockdev
dpkg-deb: building package 'sbuild-build-depends-libfprint-dummy' in '/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive/sbuild-build-depends-libfprint-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning: sbuild-build-depends-core-dummy sbuild-build-depends-libfprint-dummy
dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
gpg: using "Sbuild Signer" as default secret key for signing
Ign:1 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ InRelease
Get:2 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ Release [963 B]
Get:3 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ Release.gpg [370 B]
Get:4 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ Sources [603 B]
Get:5 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ Packages [675 B]
Fetched 2611 B in 1s (3853 B/s)
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...
Install libfprint build dependencies (apt-based resolver)
---------------------------------------------------------
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
krb5-locales libpam-cap netbase
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
autoconf automake autopoint autotools-dev bsdextrautils debhelper
dh-autoreconf dh-strip-nondeterminism docbook docbook-to-man docbook-xml
docbook-xsl dwz file fontconfig-config fonts-dejavu-core fonts-dejavu-mono
gettext gettext-base gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-gudev-1.0
gir1.2-gusb-1.0 gobject-introspection groff-base gtk-doc-tools
intltool-debian libarchive-zip-perl libblkid-dev libbrotli-dev libbrotli1
libbsd0 libcairo-gobject2 libcairo-script-interpreter2 libcairo2
libcairo2-dev libdbus-1-3 libdebhelper-perl libelf1 libexpat1 libexpat1-dev
libffi-dev libfile-stripnondeterminism-perl libfontconfig-dev libfontconfig1
libfreetype-dev libfreetype6 libgirepository-1.0-1 libgirepository1.0-dev
libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev
libglib2.0-dev-bin libgudev-1.0-0 libgudev-1.0-dev libgusb-dev libgusb2
libice-dev libice6 libicu72 liblzo2-2 libmagic-mgc libmagic1 libmount-dev
libnspr4 libnspr4-dev libnss3 libnss3-dev libosp5 libpcap0.8 libpcre2-16-0
libpcre2-32-0 libpcre2-8-0 libpcre2-dev libpcre2-posix3 libpipeline1
libpixman-1-0 libpixman-1-dev libpkgconf3 libpng-dev libpng16-16
libpthread-stubs0-dev libpython3-stdlib libpython3.11-minimal
libpython3.11-stdlib libselinux1-dev libsepol-dev libsepol2 libsm-dev libsm6
libsub-override-perl libtool libuchardet0 libudev-dev libumockdev0
libusb-1.0-0 libusb-1.0-0-dev libx11-6 libx11-data libx11-dev libxau-dev
libxau6 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev
libxcb1 libxcb1-dev libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxml2
libxrender-dev libxrender1 libxslt1.1 m4 man-db media-types meson
ninja-build opensp pkg-config pkgconf pkgconf-bin po-debconf python3
python3-cairo python3-distutils python3-gi python3-lib2to3 python3-lxml
python3-mako python3-markdown python3-markupsafe python3-minimal
python3-pkg-resources python3-pygments python3-setuptools python3.11
python3.11-minimal sgml-data umockdev uuid-dev x11-common x11proto-core-dev
x11proto-dev xml-core xorg-sgml-doctools xsltproc xtrans-dev zlib1g-dev
Suggested packages:
autoconf-archive gnu-standards autoconf-doc dh-make docbook-defguide
docbook-dsssl psgml dbtoepub docbook-xsl-doc-html | docbook-xsl-doc-pdf
| docbook-xsl-doc-text | docbook-xsl-doc docbook-xsl-saxon fop libsaxon-java
libxalan2-java libxslthl-java xalan gettext-doc libasprintf-dev
libgettextpo-dev groff dblatex libcairo2-doc freetype2-doc
libgirepository1.0-doc low-memory-monitor libglib2.0-doc
libgdk-pixbuf2.0-bin libxml2-utils libice-doc libsm-doc libtool-doc gfortran
| fortran95-compiler gcj-jdk libx11-doc libxcb-doc libxext-doc m4-doc
apparmor less www-browser doc-base libmail-box-perl python3-doc python3-tk
python3-venv python-lxml-doc python-mako-doc python3-beaker
python-markdown-doc python-pygments-doc ttf-bitstream-vera
python-setuptools-doc python3.11-venv python3.11-doc binfmt-support perlsgml
w3-recs
Recommended packages:
curl | wget | lynx dbus libarchive-cpio-perl shared-mime-info xdg-user-dirs
usb.ids libpng-tools libltdl-dev libusb-1.0-doc libmail-sendmail-perl
python3-bs4 python3-html5lib python3-yaml ca-certificates
The following NEW packages will be installed:
autoconf automake autopoint autotools-dev bsdextrautils debhelper
dh-autoreconf dh-strip-nondeterminism docbook docbook-to-man docbook-xml
docbook-xsl dwz file fontconfig-config fonts-dejavu-core fonts-dejavu-mono
gettext gettext-base gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-gudev-1.0
gir1.2-gusb-1.0 gobject-introspection groff-base gtk-doc-tools
intltool-debian libarchive-zip-perl libblkid-dev libbrotli-dev libbrotli1
libbsd0 libcairo-gobject2 libcairo-script-interpreter2 libcairo2
libcairo2-dev libdbus-1-3 libdebhelper-perl libelf1 libexpat1 libexpat1-dev
libffi-dev libfile-stripnondeterminism-perl libfontconfig-dev libfontconfig1
libfreetype-dev libfreetype6 libgirepository-1.0-1 libgirepository1.0-dev
libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev
libglib2.0-dev-bin libgudev-1.0-0 libgudev-1.0-dev libgusb-dev libgusb2
libice-dev libice6 libicu72 liblzo2-2 libmagic-mgc libmagic1 libmount-dev
libnspr4 libnspr4-dev libnss3 libnss3-dev libosp5 libpcap0.8 libpcre2-16-0
libpcre2-32-0 libpcre2-dev libpcre2-posix3 libpipeline1 libpixman-1-0
libpixman-1-dev libpkgconf3 libpng-dev libpng16-16 libpthread-stubs0-dev
libpython3-stdlib libpython3.11-minimal libpython3.11-stdlib libselinux1-dev
libsepol-dev libsm-dev libsm6 libsub-override-perl libtool libuchardet0
libudev-dev libumockdev0 libusb-1.0-0 libusb-1.0-0-dev libx11-6 libx11-data
libx11-dev libxau-dev libxau6 libxcb-render0 libxcb-render0-dev libxcb-shm0
libxcb-shm0-dev libxcb1 libxcb1-dev libxdmcp-dev libxdmcp6 libxext-dev
libxext6 libxml2 libxrender-dev libxrender1 libxslt1.1 m4 man-db media-types
meson ninja-build opensp pkg-config pkgconf pkgconf-bin po-debconf python3
python3-cairo python3-distutils python3-gi python3-lib2to3 python3-lxml
python3-mako python3-markdown python3-markupsafe python3-minimal
python3-pkg-resources python3-pygments python3-setuptools python3.11
python3.11-minimal sbuild-build-depends-libfprint-dummy sgml-data umockdev
uuid-dev x11-common x11proto-core-dev x11proto-dev xml-core
xorg-sgml-doctools xsltproc xtrans-dev zlib1g-dev
The following packages will be upgraded:
libpcre2-8-0 libsepol2
2 upgraded, 152 newly installed, 0 to remove and 4 not upgraded.
Need to get 53.0 MB of archives.
After this operation, 223 MB of additional disk space will be used.
Get:1 copy:/<<BUILDDIR>>/resolver-ZkoOF3/apt_archive ./ sbuild-build-depends-libfprint-dummy 0.invalid.0 [960 B]
Get:2 http://172.17.4.1/private trixie-staging/main armhf libpython3.11-minimal armhf 3.11.2-6 [797 kB]
Get:3 http://172.17.4.1/private trixie-staging/main armhf libexpat1 armhf 2.5.0-1 [77.2 kB]
Get:4 http://172.17.4.1/private trixie-staging/main armhf python3.11-minimal armhf 3.11.2-6 [1679 kB]
Get:5 http://172.17.4.1/private trixie-staging/main armhf python3-minimal armhf 3.11.2-1 [26.0 kB]
Get:6 http://172.17.4.1/private trixie-staging/main armhf media-types all 10.1.0 [26.9 kB]
Get:7 http://172.17.4.1/private trixie-staging/main armhf libpython3.11-stdlib armhf 3.11.2-6 [1668 kB]
Get:8 http://172.17.4.1/private trixie-staging/main armhf python3.11 armhf 3.11.2-6 [572 kB]
Get:9 http://172.17.4.1/private trixie-staging/main armhf libpython3-stdlib armhf 3.11.2-1 [9012 B]
Get:10 http://172.17.4.1/private trixie-staging/main armhf python3 armhf 3.11.2-1 [26.0 kB]
Get:11 http://172.17.4.1/private trixie-staging/main armhf libpcre2-8-0 armhf 10.42-4 [225 kB]
Get:12 http://172.17.4.1/private trixie-staging/main armhf libsepol2 armhf 3.5-1 [228 kB]
Get:13 http://172.17.4.1/private trixie-staging/main armhf libuchardet0 armhf 0.0.7-1 [65.0 kB]
Get:14 http://172.17.4.1/private trixie-staging/main armhf groff-base armhf 1.22.4-10 [774 kB]
Get:15 http://172.17.4.1/private trixie-staging/main armhf bsdextrautils armhf 2.38.1-5 [78.5 kB]
Get:16 http://172.17.4.1/private trixie-staging/main armhf libpipeline1 armhf 1.5.7-1 [33.4 kB]
Get:17 http://172.17.4.1/private trixie-staging/main armhf man-db armhf 2.11.2-2 [1342 kB]
Get:18 http://172.17.4.1/private trixie-staging/main armhf libmagic-mgc armhf 1:5.44-3 [305 kB]
Get:19 http://172.17.4.1/private trixie-staging/main armhf libmagic1 armhf 1:5.44-3 [95.3 kB]
Get:20 http://172.17.4.1/private trixie-staging/main armhf file armhf 1:5.44-3 [41.5 kB]
Get:21 http://172.17.4.1/private trixie-staging/main armhf gettext-base armhf 0.21-12 [156 kB]
Get:22 http://172.17.4.1/private trixie-staging/main armhf m4 armhf 1.4.19-3 [256 kB]
Get:23 http://172.17.4.1/private trixie-staging/main armhf autoconf all 2.71-3 [332 kB]
Get:24 http://172.17.4.1/private trixie-staging/main armhf autotools-dev all 20220109.1 [51.6 kB]
Get:25 http://172.17.4.1/private trixie-staging/main armhf automake all 1:1.16.5-1.3 [823 kB]
Get:26 http://172.17.4.1/private trixie-staging/main armhf autopoint all 0.21-13 [496 kB]
Get:27 http://172.17.4.1/private trixie-staging/main armhf libdebhelper-perl all 13.11.6 [81.9 kB]
Get:28 http://172.17.4.1/private trixie-staging/main armhf libtool all 2.4.7-7 [517 kB]
Get:29 http://172.17.4.1/private trixie-staging/main armhf dh-autoreconf all 20 [17.1 kB]
Get:30 http://172.17.4.1/private trixie-staging/main armhf libarchive-zip-perl all 1.68-1 [104 kB]
Get:31 http://172.17.4.1/private trixie-staging/main armhf libsub-override-perl all 0.09-4 [9304 B]
Get:32 http://172.17.4.1/private trixie-staging/main armhf libfile-stripnondeterminism-perl all 1.13.1-1 [19.4 kB]
Get:33 http://172.17.4.1/private trixie-staging/main armhf dh-strip-nondeterminism all 1.13.1-1 [8620 B]
Get:34 http://172.17.4.1/private trixie-staging/main armhf libelf1 armhf 0.188-2.1+rpi1 [171 kB]
Get:35 http://172.17.4.1/private trixie-staging/main armhf dwz armhf 0.15-1 [92.4 kB]
Get:36 http://172.17.4.1/private trixie-staging/main armhf libicu72 armhf 72.1-3 [9009 kB]
Get:37 http://172.17.4.1/private trixie-staging/main armhf libxml2 armhf 2.9.14+dfsg-1.3~deb12u1 [570 kB]
Get:38 http://172.17.4.1/private trixie-staging/main armhf gettext armhf 0.21-12 [1201 kB]
Get:39 http://172.17.4.1/private trixie-staging/main armhf intltool-debian all 0.35.0+20060710.6 [22.9 kB]
Get:40 http://172.17.4.1/private trixie-staging/main armhf po-debconf all 1.0.21+nmu1 [248 kB]
Get:41 http://172.17.4.1/private trixie-staging/main armhf debhelper all 13.11.6 [952 kB]
Get:42 http://172.17.4.1/private trixie-staging/main armhf xml-core all 0.18+nmu1 [23.8 kB]
Get:43 http://172.17.4.1/private trixie-staging/main armhf sgml-data all 2.0.11+nmu1 [179 kB]
Get:44 http://172.17.4.1/private trixie-staging/main armhf docbook all 4.5-10 [131 kB]
Get:45 http://172.17.4.1/private trixie-staging/main armhf libosp5 armhf 1.5.2-13 [880 kB]
Get:46 http://172.17.4.1/private trixie-staging/main armhf opensp armhf 1.5.2-13 [439 kB]
Get:47 http://172.17.4.1/private trixie-staging/main armhf docbook-to-man armhf 1:2.0.0-45 [69.1 kB]
Get:48 http://172.17.4.1/private trixie-staging/main armhf docbook-xml all 4.5-12 [85.2 kB]
Get:49 http://172.17.4.1/private trixie-staging/main armhf docbook-xsl all 1.79.2+dfsg-2 [1237 kB]
Get:50 http://172.17.4.1/private trixie-staging/main armhf fonts-dejavu-mono all 2.37-8 [489 kB]
Get:51 http://172.17.4.1/private trixie-staging/main armhf fonts-dejavu-core all 2.37-8 [840 kB]
Get:52 http://172.17.4.1/private trixie-staging/main armhf fontconfig-config armhf 2.14.1-4 [315 kB]
Get:53 http://172.17.4.1/private trixie-staging/main armhf libglib2.0-0 armhf 2.74.6-1 [1203 kB]
Get:54 http://172.17.4.1/private trixie-staging/main armhf libgirepository-1.0-1 armhf 1.74.0-3+b1 [87.5 kB]
Get:55 http://172.17.4.1/private trixie-staging/main armhf gir1.2-glib-2.0 armhf 1.74.0-3+b1 [160 kB]
Get:56 http://172.17.4.1/private trixie-staging/main armhf gir1.2-freedesktop armhf 1.74.0-3+b1 [37.5 kB]
Get:57 http://172.17.4.1/private trixie-staging/main armhf libgudev-1.0-0 armhf 237-2 [13.2 kB]
Get:58 http://172.17.4.1/private trixie-staging/main armhf gir1.2-gudev-1.0 armhf 237-2 [5372 B]
Get:59 http://172.17.4.1/private trixie-staging/main armhf libusb-1.0-0 armhf 2:1.0.26-1 [55.8 kB]
Get:60 http://172.17.4.1/private trixie-staging/main armhf libgusb2 armhf 0.3.10-1 [24.6 kB]
Get:61 http://172.17.4.1/private trixie-staging/main armhf gir1.2-gusb-1.0 armhf 0.3.10-1 [12.9 kB]
Get:62 http://172.17.4.1/private trixie-staging/main armhf python3-lib2to3 all 3.11.5-1 [77.5 kB]
Get:63 http://172.17.4.1/private trixie-staging/main armhf python3-distutils all 3.11.5-1 [131 kB]
Get:64 http://172.17.4.1/private trixie-staging/main armhf python3-pkg-resources all 68.1.2-1 [241 kB]
Get:65 http://172.17.4.1/private trixie-staging/main armhf python3-markupsafe armhf 2.1.2-1 [13.4 kB]
Get:66 http://172.17.4.1/private trixie-staging/main armhf python3-mako all 1.2.4+ds-2 [82.0 kB]
Get:67 http://172.17.4.1/private trixie-staging/main armhf python3-markdown all 3.4.4-1 [66.9 kB]
Get:68 http://172.17.4.1/private trixie-staging/main armhf gobject-introspection armhf 1.74.0-3+b1 [299 kB]
Get:69 http://172.17.4.1/private trixie-staging/main armhf libpkgconf3 armhf 1.8.1-1 [31.3 kB]
Get:70 http://172.17.4.1/private trixie-staging/main armhf pkgconf-bin armhf 1.8.1-1 [27.8 kB]
Get:71 http://172.17.4.1/private trixie-staging/main armhf pkgconf armhf 1.8.1-1 [25.9 kB]
Get:72 http://172.17.4.1/private trixie-staging/main armhf pkg-config armhf 1.8.1-1 [13.7 kB]
Get:73 http://172.17.4.1/private trixie-staging/main armhf libxslt1.1 armhf 1.1.35-1 [221 kB]
Get:74 http://172.17.4.1/private trixie-staging/main armhf python3-lxml armhf 4.9.2-1 [1528 kB]
Get:75 http://172.17.4.1/private trixie-staging/main armhf python3-pygments all 2.15.1+dfsg-1 [817 kB]
Get:76 http://172.17.4.1/private trixie-staging/main armhf xsltproc armhf 1.1.35-1 [126 kB]
Get:77 http://172.17.4.1/private trixie-staging/main armhf gtk-doc-tools all 1.33.2-1 [329 kB]
Get:78 http://172.17.4.1/private trixie-staging/main armhf uuid-dev armhf 2.38.1-5 [37.7 kB]
Get:79 http://172.17.4.1/private trixie-staging/main armhf libblkid-dev armhf 2.38.1-5 [162 kB]
Get:80 http://172.17.4.1/private trixie-staging/main armhf libbrotli1 armhf 1.0.9-2+b3 [258 kB]
Get:81 http://172.17.4.1/private trixie-staging/main armhf libbrotli-dev armhf 1.0.9-2+b3 [270 kB]
Get:82 http://172.17.4.1/private trixie-staging/main armhf libbsd0 armhf 0.11.7-4 [111 kB]
Get:83 http://172.17.4.1/private trixie-staging/main armhf libpng16-16 armhf 1.6.40-1 [258 kB]
Get:84 http://172.17.4.1/private trixie-staging/main armhf libfreetype6 armhf 2.12.1+dfsg-5 [329 kB]
Get:85 http://172.17.4.1/private trixie-staging/main armhf libfontconfig1 armhf 2.14.1-4 [366 kB]
Get:86 http://172.17.4.1/private trixie-staging/main armhf libpixman-1-0 armhf 0.42.2-1 [461 kB]
Get:87 http://172.17.4.1/private trixie-staging/main armhf libxau6 armhf 1:1.0.9-1 [19.1 kB]
Get:88 http://172.17.4.1/private trixie-staging/main armhf libxdmcp6 armhf 1:1.1.2-3 [25.0 kB]
Get:89 http://172.17.4.1/private trixie-staging/main armhf libxcb1 armhf 1.15-1 [139 kB]
Get:90 http://172.17.4.1/private trixie-staging/main armhf libx11-data all 2:1.8.6-1 [323 kB]
Get:91 http://172.17.4.1/private trixie-staging/main armhf libx11-6 armhf 2:1.8.4-2+deb12u1 [691 kB]
Get:92 http://172.17.4.1/private trixie-staging/main armhf libxcb-render0 armhf 1.15-1 [114 kB]
Get:93 http://172.17.4.1/private trixie-staging/main armhf libxcb-shm0 armhf 1.15-1 [106 kB]
Get:94 http://172.17.4.1/private trixie-staging/main armhf libxext6 armhf 2:1.3.4-1 [48.0 kB]
Get:95 http://172.17.4.1/private trixie-staging/main armhf libxrender1 armhf 1:0.9.10-1.1 [30.0 kB]
Get:96 http://172.17.4.1/private trixie-staging/main armhf libcairo2 armhf 1.16.0-7 [482 kB]
Get:97 http://172.17.4.1/private trixie-staging/main armhf libcairo-gobject2 armhf 1.16.0-7 [111 kB]
Get:98 http://172.17.4.1/private trixie-staging/main armhf liblzo2-2 armhf 2.10-2 [50.2 kB]
Get:99 http://172.17.4.1/private trixie-staging/main armhf libcairo-script-interpreter2 armhf 1.16.0-7 [139 kB]
Get:100 http://172.17.4.1/private trixie-staging/main armhf libexpat1-dev armhf 2.5.0-1 [130 kB]
Get:101 http://172.17.4.1/private trixie-staging/main armhf zlib1g-dev armhf 1:1.2.13.dfsg-1 [901 kB]
Get:102 http://172.17.4.1/private trixie-staging/main armhf libpng-dev armhf 1.6.40-1 [336 kB]
Get:103 http://172.17.4.1/private trixie-staging/main armhf libfreetype-dev armhf 2.12.1+dfsg-5 [493 kB]
Get:104 http://172.17.4.1/private trixie-staging/main armhf libfontconfig-dev armhf 2.14.1-4 [383 kB]
Get:105 http://172.17.4.1/private trixie-staging/main armhf libffi-dev armhf 3.4.4-1 [60.4 kB]
Get:106 http://172.17.4.1/private trixie-staging/main armhf libglib2.0-data all 2.78.0-1 [1236 kB]
Get:107 http://172.17.4.1/private trixie-staging/main armhf libglib2.0-bin armhf 2.74.6-1 [101 kB]
Get:108 http://172.17.4.1/private trixie-staging/main armhf libglib2.0-dev-bin armhf 2.74.6-1 [147 kB]
Get:109 http://172.17.4.1/private trixie-staging/main armhf libsepol-dev armhf 3.5-1 [309 kB]
Get:110 http://172.17.4.1/private trixie-staging/main armhf libpcre2-16-0 armhf 10.42-4 [211 kB]
Get:111 http://172.17.4.1/private trixie-staging/main armhf libpcre2-32-0 armhf 10.42-4 [201 kB]
Get:112 http://172.17.4.1/private trixie-staging/main armhf libpcre2-posix3 armhf 10.42-4 [55.1 kB]
Get:113 http://172.17.4.1/private trixie-staging/main armhf libpcre2-dev armhf 10.42-4 [648 kB]
Get:114 http://172.17.4.1/private trixie-staging/main armhf libselinux1-dev armhf 3.4-1+b2 [143 kB]
Get:115 http://172.17.4.1/private trixie-staging/main armhf libmount-dev armhf 2.38.1-5 [22.2 kB]
Get:116 http://172.17.4.1/private trixie-staging/main armhf libglib2.0-dev armhf 2.74.6-1 [1464 kB]
Get:117 http://172.17.4.1/private trixie-staging/main armhf libpixman-1-dev armhf 0.42.2-1 [480 kB]
Get:118 http://172.17.4.1/private trixie-staging/main armhf x11-common all 1:7.7+23 [252 kB]
Get:119 http://172.17.4.1/private trixie-staging/main armhf libice6 armhf 2:1.0.10-1 [51.7 kB]
Get:120 http://172.17.4.1/private trixie-staging/main armhf libsm6 armhf 2:1.2.3-1 [32.9 kB]
Get:121 http://172.17.4.1/private trixie-staging/main armhf xorg-sgml-doctools all 1:1.11-1.1 [22.1 kB]
Get:122 http://172.17.4.1/private trixie-staging/main armhf x11proto-dev all 2023.2-1 [598 kB]
Get:123 http://172.17.4.1/private trixie-staging/main armhf x11proto-core-dev all 2023.2-1 [3288 B]
Get:124 http://172.17.4.1/private trixie-staging/main armhf libice-dev armhf 2:1.0.10-1 [58.7 kB]
Get:125 http://172.17.4.1/private trixie-staging/main armhf libsm-dev armhf 2:1.2.3-1 [35.4 kB]
Get:126 http://172.17.4.1/private trixie-staging/main armhf libxau-dev armhf 1:1.0.9-1 [22.3 kB]
Get:127 http://172.17.4.1/private trixie-staging/main armhf libxdmcp-dev armhf 1:1.1.2-3 [40.9 kB]
Get:128 http://172.17.4.1/private trixie-staging/main armhf xtrans-dev all 1.4.0-1 [98.7 kB]
Get:129 http://172.17.4.1/private trixie-staging/main armhf libpthread-stubs0-dev armhf 0.4-1 [5344 B]
Get:130 http://172.17.4.1/private trixie-staging/main armhf libxcb1-dev armhf 1.15-1 [175 kB]
Get:131 http://172.17.4.1/private trixie-staging/main armhf libx11-dev armhf 2:1.8.4-2+deb12u1 [769 kB]
Get:132 http://172.17.4.1/private trixie-staging/main armhf libxcb-render0-dev armhf 1.15-1 [117 kB]
Get:133 http://172.17.4.1/private trixie-staging/main armhf libxcb-shm0-dev armhf 1.15-1 [107 kB]
Get:134 http://172.17.4.1/private trixie-staging/main armhf libxext-dev armhf 2:1.3.4-1 [102 kB]
Get:135 http://172.17.4.1/private trixie-staging/main armhf libxrender-dev armhf 1:0.9.10-1.1 [37.6 kB]
Get:136 http://172.17.4.1/private trixie-staging/main armhf libcairo2-dev armhf 1.16.0-7 [600 kB]
Get:137 http://172.17.4.1/private trixie-staging/main armhf libdbus-1-3 armhf 1.14.8-2~deb12u1 [176 kB]
Get:138 http://172.17.4.1/private trixie-staging/main armhf libgirepository1.0-dev armhf 1.74.0-3+b1 [876 kB]
Get:139 http://172.17.4.1/private trixie-staging/main armhf libudev-dev armhf 252.12-1~deb12u1+rpi1 [52.0 kB]
Get:140 http://172.17.4.1/private trixie-staging/main armhf libgudev-1.0-dev armhf 237-2 [29.0 kB]
Get:141 http://172.17.4.1/private trixie-staging/main armhf libusb-1.0-0-dev armhf 2:1.0.26-1 [73.0 kB]
Get:142 http://172.17.4.1/private trixie-staging/main armhf libgusb-dev armhf 0.3.10-1 [30.0 kB]
Get:143 http://172.17.4.1/private trixie-staging/main armhf libnspr4 armhf 2:4.35-1 [90.9 kB]
Get:144 http://172.17.4.1/private trixie-staging/main armhf libnspr4-dev armhf 2:4.35-1 [192 kB]
Get:145 http://172.17.4.1/private trixie-staging/main armhf libnss3 armhf 2:3.87.1-1 [1090 kB]
Get:146 http://172.17.4.1/private trixie-staging/main armhf libnss3-dev armhf 2:3.87.1-1 [240 kB]
Get:147 http://172.17.4.1/private trixie-staging/main armhf libpcap0.8 armhf 1.10.3-1 [140 kB]
Get:148 http://172.17.4.1/private trixie-staging/main armhf libumockdev0 armhf 0.17.18-1 [59.8 kB]
Get:149 http://172.17.4.1/private trixie-staging/main armhf ninja-build armhf 1.11.1-1 [114 kB]
Get:150 http://172.17.4.1/private trixie-staging/main armhf python3-setuptools all 68.1.2-1 [468 kB]
Get:151 http://172.17.4.1/private trixie-staging/main armhf meson all 1.2.1-3 [585 kB]
Get:152 http://172.17.4.1/private trixie-staging/main armhf python3-cairo armhf 1.20.1-5+b1 [56.1 kB]
Get:153 http://172.17.4.1/private trixie-staging/main armhf python3-gi armhf 3.42.2-3+b1 [201 kB]
Get:154 http://172.17.4.1/private trixie-staging/main armhf umockdev armhf 0.17.18-1 [70.3 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 53.0 MB in 8s (6942 kB/s)
Selecting previously unselected package libpython3.11-minimal:armhf.
(Reading database ... 11771 files and directories currently installed.)
Preparing to unpack .../libpython3.11-minimal_3.11.2-6_armhf.deb ...
Unpacking libpython3.11-minimal:armhf (3.11.2-6) ...
Selecting previously unselected package libexpat1:armhf.
Preparing to unpack .../libexpat1_2.5.0-1_armhf.deb ...
Unpacking libexpat1:armhf (2.5.0-1) ...
Selecting previously unselected package python3.11-minimal.
Preparing to unpack .../python3.11-minimal_3.11.2-6_armhf.deb ...
Unpacking python3.11-minimal (3.11.2-6) ...
Setting up libpython3.11-minimal:armhf (3.11.2-6) ...
Setting up libexpat1:armhf (2.5.0-1) ...
Setting up python3.11-minimal (3.11.2-6) ...
Selecting previously unselected package python3-minimal.
(Reading database ... 12087 files and directories currently installed.)
Preparing to unpack .../python3-minimal_3.11.2-1_armhf.deb ...
Unpacking python3-minimal (3.11.2-1) ...
Selecting previously unselected package media-types.
Preparing to unpack .../media-types_10.1.0_all.deb ...
Unpacking media-types (10.1.0) ...
Selecting previously unselected package libpython3.11-stdlib:armhf.
Preparing to unpack .../libpython3.11-stdlib_3.11.2-6_armhf.deb ...
Unpacking libpython3.11-stdlib:armhf (3.11.2-6) ...
Selecting previously unselected package python3.11.
Preparing to unpack .../python3.11_3.11.2-6_armhf.deb ...
Unpacking python3.11 (3.11.2-6) ...
Selecting previously unselected package libpython3-stdlib:armhf.
Preparing to unpack .../libpython3-stdlib_3.11.2-1_armhf.deb ...
Unpacking libpython3-stdlib:armhf (3.11.2-1) ...
Setting up python3-minimal (3.11.2-1) ...
Selecting previously unselected package python3.
(Reading database ... 12495 files and directories currently installed.)
Preparing to unpack .../python3_3.11.2-1_armhf.deb ...
Unpacking python3 (3.11.2-1) ...
Preparing to unpack .../libpcre2-8-0_10.42-4_armhf.deb ...
Unpacking libpcre2-8-0:armhf (10.42-4) over (10.42-1) ...
Setting up libpcre2-8-0:armhf (10.42-4) ...
(Reading database ... 12516 files and directories currently installed.)
Preparing to unpack .../libsepol2_3.5-1_armhf.deb ...
Unpacking libsepol2:armhf (3.5-1) over (3.4-2.1) ...
Setting up libsepol2:armhf (3.5-1) ...
Selecting previously unselected package libuchardet0:armhf.
(Reading database ... 12516 files and directories currently installed.)
Preparing to unpack .../000-libuchardet0_0.0.7-1_armhf.deb ...
Unpacking libuchardet0:armhf (0.0.7-1) ...
Selecting previously unselected package groff-base.
Preparing to unpack .../001-groff-base_1.22.4-10_armhf.deb ...
Unpacking groff-base (1.22.4-10) ...
Selecting previously unselected package bsdextrautils.
Preparing to unpack .../002-bsdextrautils_2.38.1-5_armhf.deb ...
Unpacking bsdextrautils (2.38.1-5) ...
Selecting previously unselected package libpipeline1:armhf.
Preparing to unpack .../003-libpipeline1_1.5.7-1_armhf.deb ...
Unpacking libpipeline1:armhf (1.5.7-1) ...
Selecting previously unselected package man-db.
Preparing to unpack .../004-man-db_2.11.2-2_armhf.deb ...
Unpacking man-db (2.11.2-2) ...
Selecting previously unselected package libmagic-mgc.
Preparing to unpack .../005-libmagic-mgc_1%3a5.44-3_armhf.deb ...
Unpacking libmagic-mgc (1:5.44-3) ...
Selecting previously unselected package libmagic1:armhf.
Preparing to unpack .../006-libmagic1_1%3a5.44-3_armhf.deb ...
Unpacking libmagic1:armhf (1:5.44-3) ...
Selecting previously unselected package file.
Preparing to unpack .../007-file_1%3a5.44-3_armhf.deb ...
Unpacking file (1:5.44-3) ...
Selecting previously unselected package gettext-base.
Preparing to unpack .../008-gettext-base_0.21-12_armhf.deb ...
Unpacking gettext-base (0.21-12) ...
Selecting previously unselected package m4.
Preparing to unpack .../009-m4_1.4.19-3_armhf.deb ...
Unpacking m4 (1.4.19-3) ...
Selecting previously unselected package autoconf.
Preparing to unpack .../010-autoconf_2.71-3_all.deb ...
Unpacking autoconf (2.71-3) ...
Selecting previously unselected package autotools-dev.
Preparing to unpack .../011-autotools-dev_20220109.1_all.deb ...
Unpacking autotools-dev (20220109.1) ...
Selecting previously unselected package automake.
Preparing to unpack .../012-automake_1%3a1.16.5-1.3_all.deb ...
Unpacking automake (1:1.16.5-1.3) ...
Selecting previously unselected package autopoint.
Preparing to unpack .../013-autopoint_0.21-13_all.deb ...
Unpacking autopoint (0.21-13) ...
Selecting previously unselected package libdebhelper-perl.
Preparing to unpack .../014-libdebhelper-perl_13.11.6_all.deb ...
Unpacking libdebhelper-perl (13.11.6) ...
Selecting previously unselected package libtool.
Preparing to unpack .../015-libtool_2.4.7-7_all.deb ...
Unpacking libtool (2.4.7-7) ...
Selecting previously unselected package dh-autoreconf.
Preparing to unpack .../016-dh-autoreconf_20_all.deb ...
Unpacking dh-autoreconf (20) ...
Selecting previously unselected package libarchive-zip-perl.
Preparing to unpack .../017-libarchive-zip-perl_1.68-1_all.deb ...
Unpacking libarchive-zip-perl (1.68-1) ...
Selecting previously unselected package libsub-override-perl.
Preparing to unpack .../018-libsub-override-perl_0.09-4_all.deb ...
Unpacking libsub-override-perl (0.09-4) ...
Selecting previously unselected package libfile-stripnondeterminism-perl.
Preparing to unpack .../019-libfile-stripnondeterminism-perl_1.13.1-1_all.deb ...
Unpacking libfile-stripnondeterminism-perl (1.13.1-1) ...
Selecting previously unselected package dh-strip-nondeterminism.
Preparing to unpack .../020-dh-strip-nondeterminism_1.13.1-1_all.deb ...
Unpacking dh-strip-nondeterminism (1.13.1-1) ...
Selecting previously unselected package libelf1:armhf.
Preparing to unpack .../021-libelf1_0.188-2.1+rpi1_armhf.deb ...
Unpacking libelf1:armhf (0.188-2.1+rpi1) ...
Selecting previously unselected package dwz.
Preparing to unpack .../022-dwz_0.15-1_armhf.deb ...
Unpacking dwz (0.15-1) ...
Selecting previously unselected package libicu72:armhf.
Preparing to unpack .../023-libicu72_72.1-3_armhf.deb ...
Unpacking libicu72:armhf (72.1-3) ...
Selecting previously unselected package libxml2:armhf.
Preparing to unpack .../024-libxml2_2.9.14+dfsg-1.3~deb12u1_armhf.deb ...
Unpacking libxml2:armhf (2.9.14+dfsg-1.3~deb12u1) ...
Selecting previously unselected package gettext.
Preparing to unpack .../025-gettext_0.21-12_armhf.deb ...
Unpacking gettext (0.21-12) ...
Selecting previously unselected package intltool-debian.
Preparing to unpack .../026-intltool-debian_0.35.0+20060710.6_all.deb ...
Unpacking intltool-debian (0.35.0+20060710.6) ...
Selecting previously unselected package po-debconf.
Preparing to unpack .../027-po-debconf_1.0.21+nmu1_all.deb ...
Unpacking po-debconf (1.0.21+nmu1) ...
Selecting previously unselected package debhelper.
Preparing to unpack .../028-debhelper_13.11.6_all.deb ...
Unpacking debhelper (13.11.6) ...
Selecting previously unselected package xml-core.
Preparing to unpack .../029-xml-core_0.18+nmu1_all.deb ...
Unpacking xml-core (0.18+nmu1) ...
Selecting previously unselected package sgml-data.
Preparing to unpack .../030-sgml-data_2.0.11+nmu1_all.deb ...
Unpacking sgml-data (2.0.11+nmu1) ...
Selecting previously unselected package docbook.
Preparing to unpack .../031-docbook_4.5-10_all.deb ...
Unpacking docbook (4.5-10) ...
Selecting previously unselected package libosp5.
Preparing to unpack .../032-libosp5_1.5.2-13_armhf.deb ...
Unpacking libosp5 (1.5.2-13) ...
Selecting previously unselected package opensp.
Preparing to unpack .../033-opensp_1.5.2-13_armhf.deb ...
Unpacking opensp (1.5.2-13) ...
Selecting previously unselected package docbook-to-man.
Preparing to unpack .../034-docbook-to-man_1%3a2.0.0-45_armhf.deb ...
Unpacking docbook-to-man (1:2.0.0-45) ...
Selecting previously unselected package docbook-xml.
Preparing to unpack .../035-docbook-xml_4.5-12_all.deb ...
Unpacking docbook-xml (4.5-12) ...
Selecting previously unselected package docbook-xsl.
Preparing to unpack .../036-docbook-xsl_1.79.2+dfsg-2_all.deb ...
Unpacking docbook-xsl (1.79.2+dfsg-2) ...
Selecting previously unselected package fonts-dejavu-mono.
Preparing to unpack .../037-fonts-dejavu-mono_2.37-8_all.deb ...
Unpacking fonts-dejavu-mono (2.37-8) ...
Selecting previously unselected package fonts-dejavu-core.
Preparing to unpack .../038-fonts-dejavu-core_2.37-8_all.deb ...
Unpacking fonts-dejavu-core (2.37-8) ...
Selecting previously unselected package fontconfig-config.
Preparing to unpack .../039-fontconfig-config_2.14.1-4_armhf.deb ...
Unpacking fontconfig-config (2.14.1-4) ...
Selecting previously unselected package libglib2.0-0:armhf.
Preparing to unpack .../040-libglib2.0-0_2.74.6-1_armhf.deb ...
Unpacking libglib2.0-0:armhf (2.74.6-1) ...
Selecting previously unselected package libgirepository-1.0-1:armhf.
Preparing to unpack .../041-libgirepository-1.0-1_1.74.0-3+b1_armhf.deb ...
Unpacking libgirepository-1.0-1:armhf (1.74.0-3+b1) ...
Selecting previously unselected package gir1.2-glib-2.0:armhf.
Preparing to unpack .../042-gir1.2-glib-2.0_1.74.0-3+b1_armhf.deb ...
Unpacking gir1.2-glib-2.0:armhf (1.74.0-3+b1) ...
Selecting previously unselected package gir1.2-freedesktop:armhf.
Preparing to unpack .../043-gir1.2-freedesktop_1.74.0-3+b1_armhf.deb ...
Unpacking gir1.2-freedesktop:armhf (1.74.0-3+b1) ...
Selecting previously unselected package libgudev-1.0-0:armhf.
Preparing to unpack .../044-libgudev-1.0-0_237-2_armhf.deb ...
Unpacking libgudev-1.0-0:armhf (237-2) ...
Selecting previously unselected package gir1.2-gudev-1.0:armhf.
Preparing to unpack .../045-gir1.2-gudev-1.0_237-2_armhf.deb ...
Unpacking gir1.2-gudev-1.0:armhf (237-2) ...
Selecting previously unselected package libusb-1.0-0:armhf.
Preparing to unpack .../046-libusb-1.0-0_2%3a1.0.26-1_armhf.deb ...
Unpacking libusb-1.0-0:armhf (2:1.0.26-1) ...
Selecting previously unselected package libgusb2:armhf.
Preparing to unpack .../047-libgusb2_0.3.10-1_armhf.deb ...
Unpacking libgusb2:armhf (0.3.10-1) ...
Selecting previously unselected package gir1.2-gusb-1.0:armhf.
Preparing to unpack .../048-gir1.2-gusb-1.0_0.3.10-1_armhf.deb ...
Unpacking gir1.2-gusb-1.0:armhf (0.3.10-1) ...
Selecting previously unselected package python3-lib2to3.
Preparing to unpack .../049-python3-lib2to3_3.11.5-1_all.deb ...
Unpacking python3-lib2to3 (3.11.5-1) ...
Selecting previously unselected package python3-distutils.
Preparing to unpack .../050-python3-distutils_3.11.5-1_all.deb ...
Unpacking python3-distutils (3.11.5-1) ...
Selecting previously unselected package python3-pkg-resources.
Preparing to unpack .../051-python3-pkg-resources_68.1.2-1_all.deb ...
Unpacking python3-pkg-resources (68.1.2-1) ...
Selecting previously unselected package python3-markupsafe.
Preparing to unpack .../052-python3-markupsafe_2.1.2-1_armhf.deb ...
Unpacking python3-markupsafe (2.1.2-1) ...
Selecting previously unselected package python3-mako.
Preparing to unpack .../053-python3-mako_1.2.4+ds-2_all.deb ...
Unpacking python3-mako (1.2.4+ds-2) ...
Selecting previously unselected package python3-markdown.
Preparing to unpack .../054-python3-markdown_3.4.4-1_all.deb ...
Unpacking python3-markdown (3.4.4-1) ...
Selecting previously unselected package gobject-introspection.
Preparing to unpack .../055-gobject-introspection_1.74.0-3+b1_armhf.deb ...
Unpacking gobject-introspection (1.74.0-3+b1) ...
Selecting previously unselected package libpkgconf3:armhf.
Preparing to unpack .../056-libpkgconf3_1.8.1-1_armhf.deb ...
Unpacking libpkgconf3:armhf (1.8.1-1) ...
Selecting previously unselected package pkgconf-bin.
Preparing to unpack .../057-pkgconf-bin_1.8.1-1_armhf.deb ...
Unpacking pkgconf-bin (1.8.1-1) ...
Selecting previously unselected package pkgconf:armhf.
Preparing to unpack .../058-pkgconf_1.8.1-1_armhf.deb ...
Unpacking pkgconf:armhf (1.8.1-1) ...
Selecting previously unselected package pkg-config:armhf.
Preparing to unpack .../059-pkg-config_1.8.1-1_armhf.deb ...
Unpacking pkg-config:armhf (1.8.1-1) ...
Selecting previously unselected package libxslt1.1:armhf.
Preparing to unpack .../060-libxslt1.1_1.1.35-1_armhf.deb ...
Unpacking libxslt1.1:armhf (1.1.35-1) ...
Selecting previously unselected package python3-lxml:armhf.
Preparing to unpack .../061-python3-lxml_4.9.2-1_armhf.deb ...
Unpacking python3-lxml:armhf (4.9.2-1) ...
Selecting previously unselected package python3-pygments.
Preparing to unpack .../062-python3-pygments_2.15.1+dfsg-1_all.deb ...
Unpacking python3-pygments (2.15.1+dfsg-1) ...
Selecting previously unselected package xsltproc.
Preparing to unpack .../063-xsltproc_1.1.35-1_armhf.deb ...
Unpacking xsltproc (1.1.35-1) ...
Selecting previously unselected package gtk-doc-tools.
Preparing to unpack .../064-gtk-doc-tools_1.33.2-1_all.deb ...
Unpacking gtk-doc-tools (1.33.2-1) ...
Selecting previously unselected package uuid-dev:armhf.
Preparing to unpack .../065-uuid-dev_2.38.1-5_armhf.deb ...
Unpacking uuid-dev:armhf (2.38.1-5) ...
Selecting previously unselected package libblkid-dev:armhf.
Preparing to unpack .../066-libblkid-dev_2.38.1-5_armhf.deb ...
Unpacking libblkid-dev:armhf (2.38.1-5) ...
Selecting previously unselected package libbrotli1:armhf.
Preparing to unpack .../067-libbrotli1_1.0.9-2+b3_armhf.deb ...
Unpacking libbrotli1:armhf (1.0.9-2+b3) ...
Selecting previously unselected package libbrotli-dev:armhf.
Preparing to unpack .../068-libbrotli-dev_1.0.9-2+b3_armhf.deb ...
Unpacking libbrotli-dev:armhf (1.0.9-2+b3) ...
Selecting previously unselected package libbsd0:armhf.
Preparing to unpack .../069-libbsd0_0.11.7-4_armhf.deb ...
Unpacking libbsd0:armhf (0.11.7-4) ...
Selecting previously unselected package libpng16-16:armhf.
Preparing to unpack .../070-libpng16-16_1.6.40-1_armhf.deb ...
Unpacking libpng16-16:armhf (1.6.40-1) ...
Selecting previously unselected package libfreetype6:armhf.
Preparing to unpack .../071-libfreetype6_2.12.1+dfsg-5_armhf.deb ...
Unpacking libfreetype6:armhf (2.12.1+dfsg-5) ...
Selecting previously unselected package libfontconfig1:armhf.
Preparing to unpack .../072-libfontconfig1_2.14.1-4_armhf.deb ...
Unpacking libfontconfig1:armhf (2.14.1-4) ...
Selecting previously unselected package libpixman-1-0:armhf.
Preparing to unpack .../073-libpixman-1-0_0.42.2-1_armhf.deb ...
Unpacking libpixman-1-0:armhf (0.42.2-1) ...
Selecting previously unselected package libxau6:armhf.
Preparing to unpack .../074-libxau6_1%3a1.0.9-1_armhf.deb ...
Unpacking libxau6:armhf (1:1.0.9-1) ...
Selecting previously unselected package libxdmcp6:armhf.
Preparing to unpack .../075-libxdmcp6_1%3a1.1.2-3_armhf.deb ...
Unpacking libxdmcp6:armhf (1:1.1.2-3) ...
Selecting previously unselected package libxcb1:armhf.
Preparing to unpack .../076-libxcb1_1.15-1_armhf.deb ...
Unpacking libxcb1:armhf (1.15-1) ...
Selecting previously unselected package libx11-data.
Preparing to unpack .../077-libx11-data_2%3a1.8.6-1_all.deb ...
Unpacking libx11-data (2:1.8.6-1) ...
Selecting previously unselected package libx11-6:armhf.
Preparing to unpack .../078-libx11-6_2%3a1.8.4-2+deb12u1_armhf.deb ...
Unpacking libx11-6:armhf (2:1.8.4-2+deb12u1) ...
Selecting previously unselected package libxcb-render0:armhf.
Preparing to unpack .../079-libxcb-render0_1.15-1_armhf.deb ...
Unpacking libxcb-render0:armhf (1.15-1) ...
Selecting previously unselected package libxcb-shm0:armhf.
Preparing to unpack .../080-libxcb-shm0_1.15-1_armhf.deb ...
Unpacking libxcb-shm0:armhf (1.15-1) ...
Selecting previously unselected package libxext6:armhf.
Preparing to unpack .../081-libxext6_2%3a1.3.4-1_armhf.deb ...
Unpacking libxext6:armhf (2:1.3.4-1) ...
Selecting previously unselected package libxrender1:armhf.
Preparing to unpack .../082-libxrender1_1%3a0.9.10-1.1_armhf.deb ...
Unpacking libxrender1:armhf (1:0.9.10-1.1) ...
Selecting previously unselected package libcairo2:armhf.
Preparing to unpack .../083-libcairo2_1.16.0-7_armhf.deb ...
Unpacking libcairo2:armhf (1.16.0-7) ...
Selecting previously unselected package libcairo-gobject2:armhf.
Preparing to unpack .../084-libcairo-gobject2_1.16.0-7_armhf.deb ...
Unpacking libcairo-gobject2:armhf (1.16.0-7) ...
Selecting previously unselected package liblzo2-2:armhf.
Preparing to unpack .../085-liblzo2-2_2.10-2_armhf.deb ...
Unpacking liblzo2-2:armhf (2.10-2) ...
Selecting previously unselected package libcairo-script-interpreter2:armhf.
Preparing to unpack .../086-libcairo-script-interpreter2_1.16.0-7_armhf.deb ...
Unpacking libcairo-script-interpreter2:armhf (1.16.0-7) ...
Selecting previously unselected package libexpat1-dev:armhf.
Preparing to unpack .../087-libexpat1-dev_2.5.0-1_armhf.deb ...
Unpacking libexpat1-dev:armhf (2.5.0-1) ...
Selecting previously unselected package zlib1g-dev:armhf.
Preparing to unpack .../088-zlib1g-dev_1%3a1.2.13.dfsg-1_armhf.deb ...
Unpacking zlib1g-dev:armhf (1:1.2.13.dfsg-1) ...
Selecting previously unselected package libpng-dev:armhf.
Preparing to unpack .../089-libpng-dev_1.6.40-1_armhf.deb ...
Unpacking libpng-dev:armhf (1.6.40-1) ...
Selecting previously unselected package libfreetype-dev:armhf.
Preparing to unpack .../090-libfreetype-dev_2.12.1+dfsg-5_armhf.deb ...
Unpacking libfreetype-dev:armhf (2.12.1+dfsg-5) ...
Selecting previously unselected package libfontconfig-dev:armhf.
Preparing to unpack .../091-libfontconfig-dev_2.14.1-4_armhf.deb ...
Unpacking libfontconfig-dev:armhf (2.14.1-4) ...
Selecting previously unselected package libffi-dev:armhf.
Preparing to unpack .../092-libffi-dev_3.4.4-1_armhf.deb ...
Unpacking libffi-dev:armhf (3.4.4-1) ...
Selecting previously unselected package libglib2.0-data.
Preparing to unpack .../093-libglib2.0-data_2.78.0-1_all.deb ...
Unpacking libglib2.0-data (2.78.0-1) ...
Selecting previously unselected package libglib2.0-bin.
Preparing to unpack .../094-libglib2.0-bin_2.74.6-1_armhf.deb ...
Unpacking libglib2.0-bin (2.74.6-1) ...
Selecting previously unselected package libglib2.0-dev-bin.
Preparing to unpack .../095-libglib2.0-dev-bin_2.74.6-1_armhf.deb ...
Unpacking libglib2.0-dev-bin (2.74.6-1) ...
Selecting previously unselected package libsepol-dev:armhf.
Preparing to unpack .../096-libsepol-dev_3.5-1_armhf.deb ...
Unpacking libsepol-dev:armhf (3.5-1) ...
Selecting previously unselected package libpcre2-16-0:armhf.
Preparing to unpack .../097-libpcre2-16-0_10.42-4_armhf.deb ...
Unpacking libpcre2-16-0:armhf (10.42-4) ...
Selecting previously unselected package libpcre2-32-0:armhf.
Preparing to unpack .../098-libpcre2-32-0_10.42-4_armhf.deb ...
Unpacking libpcre2-32-0:armhf (10.42-4) ...
Selecting previously unselected package libpcre2-posix3:armhf.
Preparing to unpack .../099-libpcre2-posix3_10.42-4_armhf.deb ...
Unpacking libpcre2-posix3:armhf (10.42-4) ...
Selecting previously unselected package libpcre2-dev:armhf.
Preparing to unpack .../100-libpcre2-dev_10.42-4_armhf.deb ...
Unpacking libpcre2-dev:armhf (10.42-4) ...
Selecting previously unselected package libselinux1-dev:armhf.
Preparing to unpack .../101-libselinux1-dev_3.4-1+b2_armhf.deb ...
Unpacking libselinux1-dev:armhf (3.4-1+b2) ...
Selecting previously unselected package libmount-dev:armhf.
Preparing to unpack .../102-libmount-dev_2.38.1-5_armhf.deb ...
Unpacking libmount-dev:armhf (2.38.1-5) ...
Selecting previously unselected package libglib2.0-dev:armhf.
Preparing to unpack .../103-libglib2.0-dev_2.74.6-1_armhf.deb ...
Unpacking libglib2.0-dev:armhf (2.74.6-1) ...
Selecting previously unselected package libpixman-1-dev:armhf.
Preparing to unpack .../104-libpixman-1-dev_0.42.2-1_armhf.deb ...
Unpacking libpixman-1-dev:armhf (0.42.2-1) ...
Selecting previously unselected package x11-common.
Preparing to unpack .../105-x11-common_1%3a7.7+23_all.deb ...
Unpacking x11-common (1:7.7+23) ...
Selecting previously unselected package libice6:armhf.
Preparing to unpack .../106-libice6_2%3a1.0.10-1_armhf.deb ...
Unpacking libice6:armhf (2:1.0.10-1) ...
Selecting previously unselected package libsm6:armhf.
Preparing to unpack .../107-libsm6_2%3a1.2.3-1_armhf.deb ...
Unpacking libsm6:armhf (2:1.2.3-1) ...
Selecting previously unselected package xorg-sgml-doctools.
Preparing to unpack .../108-xorg-sgml-doctools_1%3a1.11-1.1_all.deb ...
Unpacking xorg-sgml-doctools (1:1.11-1.1) ...
Selecting previously unselected package x11proto-dev.
Preparing to unpack .../109-x11proto-dev_2023.2-1_all.deb ...
Unpacking x11proto-dev (2023.2-1) ...
Selecting previously unselected package x11proto-core-dev.
Preparing to unpack .../110-x11proto-core-dev_2023.2-1_all.deb ...
Unpacking x11proto-core-dev (2023.2-1) ...
Selecting previously unselected package libice-dev:armhf.
Preparing to unpack .../111-libice-dev_2%3a1.0.10-1_armhf.deb ...
Unpacking libice-dev:armhf (2:1.0.10-1) ...
Selecting previously unselected package libsm-dev:armhf.
Preparing to unpack .../112-libsm-dev_2%3a1.2.3-1_armhf.deb ...
Unpacking libsm-dev:armhf (2:1.2.3-1) ...
Selecting previously unselected package libxau-dev:armhf.
Preparing to unpack .../113-libxau-dev_1%3a1.0.9-1_armhf.deb ...
Unpacking libxau-dev:armhf (1:1.0.9-1) ...
Selecting previously unselected package libxdmcp-dev:armhf.
Preparing to unpack .../114-libxdmcp-dev_1%3a1.1.2-3_armhf.deb ...
Unpacking libxdmcp-dev:armhf (1:1.1.2-3) ...
Selecting previously unselected package xtrans-dev.
Preparing to unpack .../115-xtrans-dev_1.4.0-1_all.deb ...
Unpacking xtrans-dev (1.4.0-1) ...
Selecting previously unselected package libpthread-stubs0-dev:armhf.
Preparing to unpack .../116-libpthread-stubs0-dev_0.4-1_armhf.deb ...
Unpacking libpthread-stubs0-dev:armhf (0.4-1) ...
Selecting previously unselected package libxcb1-dev:armhf.
Preparing to unpack .../117-libxcb1-dev_1.15-1_armhf.deb ...
Unpacking libxcb1-dev:armhf (1.15-1) ...
Selecting previously unselected package libx11-dev:armhf.
Preparing to unpack .../118-libx11-dev_2%3a1.8.4-2+deb12u1_armhf.deb ...
Unpacking libx11-dev:armhf (2:1.8.4-2+deb12u1) ...
Selecting previously unselected package libxcb-render0-dev:armhf.
Preparing to unpack .../119-libxcb-render0-dev_1.15-1_armhf.deb ...
Unpacking libxcb-render0-dev:armhf (1.15-1) ...
Selecting previously unselected package libxcb-shm0-dev:armhf.
Preparing to unpack .../120-libxcb-shm0-dev_1.15-1_armhf.deb ...
Unpacking libxcb-shm0-dev:armhf (1.15-1) ...
Selecting previously unselected package libxext-dev:armhf.
Preparing to unpack .../121-libxext-dev_2%3a1.3.4-1_armhf.deb ...
Unpacking libxext-dev:armhf (2:1.3.4-1) ...
Selecting previously unselected package libxrender-dev:armhf.
Preparing to unpack .../122-libxrender-dev_1%3a0.9.10-1.1_armhf.deb ...
Unpacking libxrender-dev:armhf (1:0.9.10-1.1) ...
Selecting previously unselected package libcairo2-dev:armhf.
Preparing to unpack .../123-libcairo2-dev_1.16.0-7_armhf.deb ...
Unpacking libcairo2-dev:armhf (1.16.0-7) ...
Selecting previously unselected package libdbus-1-3:armhf.
Preparing to unpack .../124-libdbus-1-3_1.14.8-2~deb12u1_armhf.deb ...
Unpacking libdbus-1-3:armhf (1.14.8-2~deb12u1) ...
Selecting previously unselected package libgirepository1.0-dev.
Preparing to unpack .../125-libgirepository1.0-dev_1.74.0-3+b1_armhf.deb ...
Unpacking libgirepository1.0-dev (1.74.0-3+b1) ...
Selecting previously unselected package libudev-dev:armhf.
Preparing to unpack .../126-libudev-dev_252.12-1~deb12u1+rpi1_armhf.deb ...
Unpacking libudev-dev:armhf (252.12-1~deb12u1+rpi1) ...
Selecting previously unselected package libgudev-1.0-dev:armhf.
Preparing to unpack .../127-libgudev-1.0-dev_237-2_armhf.deb ...
Unpacking libgudev-1.0-dev:armhf (237-2) ...
Selecting previously unselected package libusb-1.0-0-dev:armhf.
Preparing to unpack .../128-libusb-1.0-0-dev_2%3a1.0.26-1_armhf.deb ...
Unpacking libusb-1.0-0-dev:armhf (2:1.0.26-1) ...
Selecting previously unselected package libgusb-dev.
Preparing to unpack .../129-libgusb-dev_0.3.10-1_armhf.deb ...
Unpacking libgusb-dev (0.3.10-1) ...
Selecting previously unselected package libnspr4:armhf.
Preparing to unpack .../130-libnspr4_2%3a4.35-1_armhf.deb ...
Unpacking libnspr4:armhf (2:4.35-1) ...
Selecting previously unselected package libnspr4-dev.
Preparing to unpack .../131-libnspr4-dev_2%3a4.35-1_armhf.deb ...
Unpacking libnspr4-dev (2:4.35-1) ...
Selecting previously unselected package libnss3:armhf.
Preparing to unpack .../132-libnss3_2%3a3.87.1-1_armhf.deb ...
Unpacking libnss3:armhf (2:3.87.1-1) ...
Selecting previously unselected package libnss3-dev:armhf.
Preparing to unpack .../133-libnss3-dev_2%3a3.87.1-1_armhf.deb ...
Unpacking libnss3-dev:armhf (2:3.87.1-1) ...
Selecting previously unselected package libpcap0.8:armhf.
Preparing to unpack .../134-libpcap0.8_1.10.3-1_armhf.deb ...
Unpacking libpcap0.8:armhf (1.10.3-1) ...
Selecting previously unselected package libumockdev0:armhf.
Preparing to unpack .../135-libumockdev0_0.17.18-1_armhf.deb ...
Unpacking libumockdev0:armhf (0.17.18-1) ...
Selecting previously unselected package ninja-build.
Preparing to unpack .../136-ninja-build_1.11.1-1_armhf.deb ...
Unpacking ninja-build (1.11.1-1) ...
Selecting previously unselected package python3-setuptools.
Preparing to unpack .../137-python3-setuptools_68.1.2-1_all.deb ...
Unpacking python3-setuptools (68.1.2-1) ...
Selecting previously unselected package meson.
Preparing to unpack .../138-meson_1.2.1-3_all.deb ...
Unpacking meson (1.2.1-3) ...
Selecting previously unselected package python3-cairo:armhf.
Preparing to unpack .../139-python3-cairo_1.20.1-5+b1_armhf.deb ...
Unpacking python3-cairo:armhf (1.20.1-5+b1) ...
Selecting previously unselected package python3-gi.
Preparing to unpack .../140-python3-gi_3.42.2-3+b1_armhf.deb ...
Unpacking python3-gi (3.42.2-3+b1) ...
Selecting previously unselected package umockdev.
Preparing to unpack .../141-umockdev_0.17.18-1_armhf.deb ...
Unpacking umockdev (0.17.18-1) ...
Selecting previously unselected package sbuild-build-depends-libfprint-dummy.
Preparing to unpack .../142-sbuild-build-depends-libfprint-dummy_0.invalid.0_armhf.deb ...
Unpacking sbuild-build-depends-libfprint-dummy (0.invalid.0) ...
Setting up media-types (10.1.0) ...
Setting up libpipeline1:armhf (1.5.7-1) ...
Setting up libpixman-1-0:armhf (0.42.2-1) ...
Setting up libxau6:armhf (1:1.0.9-1) ...
Setting up libpixman-1-dev:armhf (0.42.2-1) ...
Setting up libicu72:armhf (72.1-3) ...
Setting up bsdextrautils (2.38.1-5) ...
Setting up libmagic-mgc (1:5.44-3) ...
Setting up libarchive-zip-perl (1.68-1) ...
Setting up libglib2.0-0:armhf (2.74.6-1) ...
No schema files found: doing nothing.
Setting up libpython3.11-stdlib:armhf (3.11.2-6) ...
Setting up libdebhelper-perl (13.11.6) ...
Setting up libbrotli1:armhf (1.0.9-2+b3) ...
Setting up x11-common (1:7.7+23) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of restart.
Setting up libmagic1:armhf (1:5.44-3) ...
Setting up gettext-base (0.21-12) ...
Setting up m4 (1.4.19-3) ...
Setting up liblzo2-2:armhf (2.10-2) ...
Setting up file (1:5.44-3) ...
Setting up libffi-dev:armhf (3.4.4-1) ...
Setting up libpthread-stubs0-dev:armhf (0.4-1) ...
Setting up libpcre2-16-0:armhf (10.42-4) ...
Setting up ninja-build (1.11.1-1) ...
Setting up libosp5 (1.5.2-13) ...
Setting up xtrans-dev (1.4.0-1) ...
Setting up autotools-dev (20220109.1) ...
Setting up libpcre2-32-0:armhf (10.42-4) ...
Setting up libglib2.0-data (2.78.0-1) ...
Setting up libpkgconf3:armhf (1.8.1-1) ...
Setting up libexpat1-dev:armhf (2.5.0-1) ...
Setting up libx11-data (2:1.8.6-1) ...
Setting up libnspr4:armhf (2:4.35-1) ...
Setting up uuid-dev:armhf (2.38.1-5) ...
Setting up libdbus-1-3:armhf (1.14.8-2~deb12u1) ...
Setting up fonts-dejavu-mono (2.37-8) ...
Setting up libpng16-16:armhf (1.6.40-1) ...
Setting up autopoint (0.21-13) ...
Setting up fonts-dejavu-core (2.37-8) ...
Setting up libudev-dev:armhf (252.12-1~deb12u1+rpi1) ...
Setting up libsepol-dev:armhf (3.5-1) ...
Setting up pkgconf-bin (1.8.1-1) ...
Setting up autoconf (2.71-3) ...
Setting up zlib1g-dev:armhf (1:1.2.13.dfsg-1) ...
Setting up libpcre2-posix3:armhf (10.42-4) ...
Setting up xml-core (0.18+nmu1) ...
Setting up libuchardet0:armhf (0.0.7-1) ...
Setting up libsub-override-perl (0.09-4) ...
Setting up libgirepository-1.0-1:armhf (1.74.0-3+b1) ...
Setting up xorg-sgml-doctools (1:1.11-1.1) ...
Setting up libusb-1.0-0:armhf (2:1.0.26-1) ...
Setting up libbsd0:armhf (0.11.7-4) ...
Setting up libelf1:armhf (0.188-2.1+rpi1) ...
Setting up libxml2:armhf (2.9.14+dfsg-1.3~deb12u1) ...
Setting up libbrotli-dev:armhf (1.0.9-2+b3) ...
Setting up libgudev-1.0-0:armhf (237-2) ...
Setting up libpython3-stdlib:armhf (3.11.2-1) ...
Setting up automake (1:1.16.5-1.3) ...
update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode
Setting up libfile-stripnondeterminism-perl (1.13.1-1) ...
Setting up libnspr4-dev (2:4.35-1) ...
Setting up libblkid-dev:armhf (2.38.1-5) ...
Setting up python3.11 (3.11.2-6) ...
Setting up libice6:armhf (2:1.0.10-1) ...
Setting up libxdmcp6:armhf (1:1.1.2-3) ...
Setting up libxcb1:armhf (1.15-1) ...
Setting up gettext (0.21-12) ...
Setting up libpcre2-dev:armhf (10.42-4) ...
Setting up libtool (2.4.7-7) ...
Setting up libxcb-render0:armhf (1.15-1) ...
Setting up libselinux1-dev:armhf (3.4-1+b2) ...
Setting up fontconfig-config (2.14.1-4) ...
Setting up libgusb2:armhf (0.3.10-1) ...
Setting up libpng-dev:armhf (1.6.40-1) ...
Setting up libglib2.0-bin (2.74.6-1) ...
Setting up libusb-1.0-0-dev:armhf (2:1.0.26-1) ...
Setting up python3 (3.11.2-1) ...
Setting up libnss3:armhf (2:3.87.1-1) ...
Setting up libxcb-shm0:armhf (1.15-1) ...
Setting up opensp (1.5.2-13) ...
Setting up python3-markupsafe (2.1.2-1) ...
Setting up pkgconf:armhf (1.8.1-1) ...
Setting up intltool-debian (0.35.0+20060710.6) ...
Setting up dh-autoreconf (20) ...
Setting up libfreetype6:armhf (2.12.1+dfsg-5) ...
Setting up libpcap0.8:armhf (1.10.3-1) ...
Setting up python3-markdown (3.4.4-1) ...
Setting up pkg-config:armhf (1.8.1-1) ...
Setting up libumockdev0:armhf (0.17.18-1) ...
Setting up gir1.2-glib-2.0:armhf (1.74.0-3+b1) ...
Setting up dh-strip-nondeterminism (1.13.1-1) ...
Setting up dwz (0.15-1) ...
Setting up libnss3-dev:armhf (2:3.87.1-1) ...
Setting up groff-base (1.22.4-10) ...
Setting up libxslt1.1:armhf (1.1.35-1) ...
Setting up libx11-6:armhf (2:1.8.4-2+deb12u1) ...
Setting up python3-lib2to3 (3.11.5-1) ...
Setting up libsm6:armhf (2:1.2.3-1) ...
Setting up libmount-dev:armhf (2.38.1-5) ...
Setting up python3-pkg-resources (68.1.2-1) ...
Setting up python3-distutils (3.11.5-1) ...
Setting up libglib2.0-dev-bin (2.74.6-1) ...
Setting up gir1.2-freedesktop:armhf (1.74.0-3+b1) ...
Setting up python3-setuptools (68.1.2-1) ...
Setting up libxrender1:armhf (1:0.9.10-1.1) ...
Setting up umockdev (0.17.18-1) ...
Setting up po-debconf (1.0.21+nmu1) ...
Setting up xsltproc (1.1.35-1) ...
Setting up libxext6:armhf (2:1.3.4-1) ...
Setting up meson (1.2.1-3) ...
Setting up gir1.2-gusb-1.0:armhf (0.3.10-1) ...
Setting up man-db (2.11.2-2) ...
Not building database; man-db/auto-update is not 'true'.
Setting up libfreetype-dev:armhf (2.12.1+dfsg-5) ...
Setting up python3-pygments (2.15.1+dfsg-1) ...
Setting up libglib2.0-dev:armhf (2.74.6-1) ...
Setting up python3-gi (3.42.2-3+b1) ...
Setting up gir1.2-gudev-1.0:armhf (237-2) ...
Setting up python3-lxml:armhf (4.9.2-1) ...
Setting up python3-mako (1.2.4+ds-2) ...
Setting up libgusb-dev (0.3.10-1) ...
Setting up libgudev-1.0-dev:armhf (237-2) ...
Setting up gobject-introspection (1.74.0-3+b1) ...
Setting up debhelper (13.11.6) ...
Setting up libgirepository1.0-dev (1.74.0-3+b1) ...
Processing triggers for libc-bin (2.36-9+rpi1+deb12u1) ...
Processing triggers for sgml-base (1.31) ...
Setting up sgml-data (2.0.11+nmu1) ...
Setting up libfontconfig1:armhf (2.14.1-4) ...
Setting up x11proto-dev (2023.2-1) ...
Setting up libxau-dev:armhf (1:1.0.9-1) ...
Setting up libice-dev:armhf (2:1.0.10-1) ...
Setting up libfontconfig-dev:armhf (2.14.1-4) ...
Setting up libsm-dev:armhf (2:1.2.3-1) ...
Setting up libcairo2:armhf (1.16.0-7) ...
Setting up libxdmcp-dev:armhf (1:1.1.2-3) ...
Setting up x11proto-core-dev (2023.2-1) ...
Setting up docbook-xsl (1.79.2+dfsg-2) ...
Setting up libcairo-gobject2:armhf (1.16.0-7) ...
Setting up libcairo-script-interpreter2:armhf (1.16.0-7) ...
Setting up libxcb1-dev:armhf (1.15-1) ...
Setting up python3-cairo:armhf (1.20.1-5+b1) ...
Setting up libx11-dev:armhf (2:1.8.4-2+deb12u1) ...
Setting up libxcb-shm0-dev:armhf (1.15-1) ...
Setting up libxcb-render0-dev:armhf (1.15-1) ...
Setting up libxext-dev:armhf (2:1.3.4-1) ...
Setting up libxrender-dev:armhf (1:0.9.10-1.1) ...
Setting up libcairo2-dev:armhf (1.16.0-7) ...
Processing triggers for sgml-base (1.31) ...
Setting up docbook-xml (4.5-12) ...
Setting up docbook (4.5-10) ...
Processing triggers for sgml-base (1.31) ...
Setting up docbook-to-man (1:2.0.0-45) ...
Setting up gtk-doc-tools (1.33.2-1) ...
Setting up sbuild-build-depends-libfprint-dummy (0.invalid.0) ...
Processing triggers for libc-bin (2.36-9+rpi1+deb12u1) ...
W: No sandbox user '_apt' on the system, can not drop privileges
+------------------------------------------------------------------------------+
| Build environment |
+------------------------------------------------------------------------------+
Kernel: Linux 4.15.0-187-generic armhf (armv8l)
Toolchain package versions: binutils_2.40-2+rpi2 dpkg-dev_1.21.22+rpi1 g++-12_12.2.0-14+rpi1 gcc-12_12.2.0-14+rpi1 libc6-dev_2.36-9+rpi1+deb12u1 libstdc++-12-dev_12.2.0-14+rpi1 libstdc++6_12.2.0-14+rpi1 linux-libc-dev_6.1.38-1+rpi1
Package versions: adduser_3.137 apt_2.6.1 autoconf_2.71-3 automake_1:1.16.5-1.3 autopoint_0.21-13 autotools-dev_20220109.1 base-files_12.4+rpi1+deb12u1 base-passwd_3.6.1 bash_5.2.15-2 binutils_2.40-2+rpi2 binutils-arm-linux-gnueabihf_2.40-2+rpi2 binutils-common_2.40-2+rpi2 bsdextrautils_2.38.1-5 bsdutils_1:2.38.1-5 build-essential_12.9 bzip2_1.0.8-5+b2 coreutils_9.1-1 cpp_4:12.2.0-3+rpi1 cpp-12_12.2.0-14+rpi1 dash_0.5.12-2 debconf_1.5.82 debhelper_13.11.6 debianutils_5.7-0.4 dh-autoreconf_20 dh-strip-nondeterminism_1.13.1-1 diffutils_1:3.8-4 dirmngr_2.2.40-1.1 docbook_4.5-10 docbook-to-man_1:2.0.0-45 docbook-xml_4.5-12 docbook-xsl_1.79.2+dfsg-2 dpkg_1.21.22+rpi1 dpkg-dev_1.21.22+rpi1 dwz_0.15-1 e2fsprogs_1.47.0-2 fakeroot_1.31-1.2 file_1:5.44-3 findutils_4.9.0-4 fontconfig-config_2.14.1-4 fonts-dejavu-core_2.37-8 fonts-dejavu-mono_2.37-8 g++_4:12.2.0-3+rpi1 g++-12_12.2.0-14+rpi1 gcc_4:12.2.0-3+rpi1 gcc-12_12.2.0-14+rpi1 gcc-12-base_12.2.0-14+rpi1 gcc-7-base_7.5.0-6+rpi1+b2 gcc-8-base_8.4.0-7+rpi1 gcc-9-base_9.4.0-2+rpi1 gettext_0.21-12 gettext-base_0.21-12 gir1.2-freedesktop_1.74.0-3+b1 gir1.2-glib-2.0_1.74.0-3+b1 gir1.2-gudev-1.0_237-2 gir1.2-gusb-1.0_0.3.10-1 gnupg_2.2.40-1.1 gnupg-l10n_2.2.40-1.1 gnupg-utils_2.2.40-1.1 gobject-introspection_1.74.0-3+b1 gpg_2.2.40-1.1 gpg-agent_2.2.40-1.1 gpg-wks-client_2.2.40-1.1 gpg-wks-server_2.2.40-1.1 gpgconf_2.2.40-1.1 gpgsm_2.2.40-1.1 gpgv_2.2.40-1.1 grep_3.8-5 groff-base_1.22.4-10 gtk-doc-tools_1.33.2-1 gzip_1.12-1 hostname_3.23+nmu1 init-system-helpers_1.65.2 intltool-debian_0.35.0+20060710.6 iputils-ping_3:20221126-1 krb5-locales_1.20.1-3 libacl1_2.3.1-3 libapt-pkg6.0_2.6.1 libarchive-zip-perl_1.68-1 libasan8_12.2.0-14+rpi1 libassuan0_2.5.5-5 libatomic1_12.2.0-14+rpi1 libattr1_1:2.5.1-4 libaudit-common_1:3.1.1-1 libaudit1_1:3.0.9-1 libbinutils_2.40-2+rpi2 libblkid-dev_2.38.1-5 libblkid1_2.38.1-5 libbrotli-dev_1.0.9-2+b3 libbrotli1_1.0.9-2+b3 libbsd0_0.11.7-4 libbz2-1.0_1.0.8-5+b2 libc-bin_2.36-9+rpi1+deb12u1 libc-dev-bin_2.36-9+rpi1+deb12u1 libc6_2.36-9+rpi1+deb12u1 libc6-dev_2.36-9+rpi1+deb12u1 libcairo-gobject2_1.16.0-7 libcairo-script-interpreter2_1.16.0-7 libcairo2_1.16.0-7 libcairo2-dev_1.16.0-7 libcap-ng0_0.8.3-1+b1 libcap2_1:2.66-4 libcap2-bin_1:2.66-4 libcc1-0_12.2.0-14+rpi1 libcom-err2_1.47.0-2 libcrypt-dev_1:4.4.33-2 libcrypt1_1:4.4.33-2 libctf-nobfd0_2.40-2+rpi2 libctf0_2.40-2+rpi2 libdb5.3_5.3.28+dfsg2-1 libdbus-1-3_1.14.8-2~deb12u1 libdebconfclient0_0.270 libdebhelper-perl_13.11.6 libdpkg-perl_1.21.22+rpi1 libelf1_0.188-2.1+rpi1 libexpat1_2.5.0-1 libexpat1-dev_2.5.0-1 libext2fs2_1.47.0-2 libfakeroot_1.31-1.2 libffi-dev_3.4.4-1 libffi8_3.4.4-1 libfile-find-rule-perl_0.34-3 libfile-stripnondeterminism-perl_1.13.1-1 libfontconfig-dev_2.14.1-4 libfontconfig1_2.14.1-4 libfreetype-dev_2.12.1+dfsg-5 libfreetype6_2.12.1+dfsg-5 libgcc-12-dev_12.2.0-14+rpi1 libgcc-s1_12.2.0-14+rpi1 libgcrypt20_1.10.1-3 libgdbm-compat4_1.23-3 libgdbm6_1.23-3 libgirepository-1.0-1_1.74.0-3+b1 libgirepository1.0-dev_1.74.0-3+b1 libglib2.0-0_2.74.6-1 libglib2.0-bin_2.74.6-1 libglib2.0-data_2.78.0-1 libglib2.0-dev_2.74.6-1 libglib2.0-dev-bin_2.74.6-1 libgmp10_2:6.2.1+dfsg1-1.1 libgnutls30_3.7.9-2 libgomp1_12.2.0-14+rpi1 libgpg-error0_1.46-1 libgssapi-krb5-2_1.20.1-2 libgudev-1.0-0_237-2 libgudev-1.0-dev_237-2 libgusb-dev_0.3.10-1 libgusb2_0.3.10-1 libhogweed6_3.8.1-2 libice-dev_2:1.0.10-1 libice6_2:1.0.10-1 libicu72_72.1-3 libidn2-0_2.3.3-1+b2 libisl23_0.25-1 libjansson4_2.14-2 libk5crypto3_1.20.1-2 libkeyutils1_1.6.3-2 libkrb5-3_1.20.1-2 libkrb5support0_1.20.1-2 libksba8_1.6.3-2 libldap-2.5-0_2.5.13+dfsg-5+rpi1 liblz4-1_1.9.4-1+rpi1+b1 liblzma5_5.4.1-0.2 liblzo2-2_2.10-2 libmagic-mgc_1:5.44-3 libmagic1_1:5.44-3 libmd0_1.0.4-2 libmount-dev_2.38.1-5 libmount1_2.38.1-5 libmpc3_1.3.1-1 libmpfr6_4.2.0-1 libncursesw6_6.4-4 libnettle8_3.8.1-2 libnpth0_1.6-3 libnsl-dev_1.3.0-2 libnsl2_1.3.0-2 libnspr4_2:4.35-1 libnspr4-dev_2:4.35-1 libnss3_2:3.87.1-1 libnss3-dev_2:3.87.1-1 libnumber-compare-perl_0.03-3 libosp5_1.5.2-13 libp11-kit0_0.24.1-2 libpam-cap_1:2.66-4 libpam-modules_1.5.2-6 libpam-modules-bin_1.5.2-6 libpam-runtime_1.5.2-7 libpam0g_1.5.2-6 libpcap0.8_1.10.3-1 libpcre2-16-0_10.42-4 libpcre2-32-0_10.42-4 libpcre2-8-0_10.42-4 libpcre2-dev_10.42-4 libpcre2-posix3_10.42-4 libpcre3_2:8.39-15 libperl5.36_5.36.0-7 libpipeline1_1.5.7-1 libpixman-1-0_0.42.2-1 libpixman-1-dev_0.42.2-1 libpkgconf3_1.8.1-1 libpng-dev_1.6.40-1 libpng16-16_1.6.40-1 libpthread-stubs0-dev_0.4-1 libpython3-stdlib_3.11.2-1 libpython3.11-minimal_3.11.2-6 libpython3.11-stdlib_3.11.2-6 libreadline8_8.2-1.3 libsasl2-2_2.1.28+dfsg-10 libsasl2-modules-db_2.1.28+dfsg-10 libseccomp2_2.5.4-1+rpi1+b1 libselinux1_3.4-1+b2 libselinux1-dev_3.4-1+b2 libsemanage-common_3.5-1 libsemanage2_3.4-1+b2 libsepol-dev_3.5-1 libsepol1_3.1-1 libsepol2_3.5-1 libsm-dev_2:1.2.3-1 libsm6_2:1.2.3-1 libsmartcols1_2.38.1-5 libsqlite3-0_3.40.1-2 libss2_1.47.0-2 libssl1.1_1.1.1o-1 libssl3_3.0.9-1 libstdc++-12-dev_12.2.0-14+rpi1 libstdc++6_12.2.0-14+rpi1 libsub-override-perl_0.09-4 libsystemd0_252.12-1~deb12u1+rpi1 libtasn1-6_4.19.0-2 libtext-glob-perl_0.11-3 libtinfo6_6.4-4 libtirpc-common_1.3.3+ds-1 libtirpc-dev_1.3.3+ds-1 libtirpc3_1.3.3+ds-1 libtool_2.4.7-7 libubsan1_12.2.0-14+rpi1 libuchardet0_0.0.7-1 libudev-dev_252.12-1~deb12u1+rpi1 libudev1_252.12-1~deb12u1+rpi1 libumockdev0_0.17.18-1 libunistring2_1.0-2 libusb-1.0-0_2:1.0.26-1 libusb-1.0-0-dev_2:1.0.26-1 libuuid1_2.38.1-5 libx11-6_2:1.8.4-2+deb12u1 libx11-data_2:1.8.6-1 libx11-dev_2:1.8.4-2+deb12u1 libxau-dev_1:1.0.9-1 libxau6_1:1.0.9-1 libxcb-render0_1.15-1 libxcb-render0-dev_1.15-1 libxcb-shm0_1.15-1 libxcb-shm0-dev_1.15-1 libxcb1_1.15-1 libxcb1-dev_1.15-1 libxdmcp-dev_1:1.1.2-3 libxdmcp6_1:1.1.2-3 libxext-dev_2:1.3.4-1 libxext6_2:1.3.4-1 libxml2_2.9.14+dfsg-1.3~deb12u1 libxrender-dev_1:0.9.10-1.1 libxrender1_1:0.9.10-1.1 libxslt1.1_1.1.35-1 libxxhash0_0.8.1-1 libzstd1_1.5.4+dfsg2-5 linux-libc-dev_6.1.38-1+rpi1 login_1:4.13+dfsg1-1 logsave_1.47.0-2 lsb-base_11.6+rpi1 m4_1.4.19-3 make_4.3-4.1 man-db_2.11.2-2 mawk_1.3.4.20200120-3.1 media-types_10.1.0 meson_1.2.1-3 mount_2.38.1-5 nano_7.2-1 ncurses-base_6.4+20230625-2 ncurses-bin_6.4-4 netbase_6.4 ninja-build_1.11.1-1 opensp_1.5.2-13 passwd_1:4.13+dfsg1-1 patch_2.7.6-7 perl_5.36.0-7 perl-base_5.36.0-7 perl-modules-5.36_5.36.0-7 pinentry-curses_1.2.1-1 pkg-config_1.8.1-1 pkgconf_1.8.1-1 pkgconf-bin_1.8.1-1 po-debconf_1.0.21+nmu1 python3_3.11.2-1 python3-cairo_1.20.1-5+b1 python3-distutils_3.11.5-1 python3-gi_3.42.2-3+b1 python3-lib2to3_3.11.5-1 python3-lxml_4.9.2-1 python3-mako_1.2.4+ds-2 python3-markdown_3.4.4-1 python3-markupsafe_2.1.2-1 python3-minimal_3.11.2-1 python3-pkg-resources_68.1.2-1 python3-pygments_2.15.1+dfsg-1 python3-setuptools_68.1.2-1 python3.11_3.11.2-6 python3.11-minimal_3.11.2-6 raspbian-archive-keyring_20120528.2 readline-common_8.2-1.3 rpcsvc-proto_1.4.3-1 sbuild-build-depends-core-dummy_0.invalid.0 sbuild-build-depends-libfprint-dummy_0.invalid.0 sed_4.9-1 sensible-utils_0.0.20 sgml-base_1.31 sgml-data_2.0.11+nmu1 sysvinit-utils_3.06-4 tar_1.34+dfsg-1.2 tzdata_2023c-10 umockdev_0.17.18-1 usrmerge_37 util-linux_2.38.1-5 util-linux-extra_2.38.1-5 uuid-dev_2.38.1-5 x11-common_1:7.7+23 x11proto-core-dev_2023.2-1 x11proto-dev_2023.2-1 xml-core_0.18+nmu1 xorg-sgml-doctools_1:1.11-1.1 xsltproc_1.1.35-1 xtrans-dev_1.4.0-1 xz-utils_5.4.1-0.2 zlib1g_1:1.2.13.dfsg-1 zlib1g-dev_1:1.2.13.dfsg-1
+------------------------------------------------------------------------------+
| Build |
+------------------------------------------------------------------------------+
Unpack source
-------------
gpgv: Signature made Thu Aug 24 07:19:53 2023 UTC
gpgv: using RSA key D4C501DA48EB797A081750939449C2F50996635F
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.6-2.dsc: no acceptable signature found
dpkg-source: info: extracting libfprint in /<<PKGBUILDDIR>>
dpkg-source: info: unpacking libfprint_1.94.6.orig.tar.bz2
dpkg-source: info: unpacking libfprint_1.94.6-2.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying tests-Use-native-GTest-utils-to-generate-assets-names.patch
dpkg-source: warning: diff '/<<PKGBUILDDIR>>/debian/patches/tests-egis0570-capture.pcapng-Remove-execution-permission.patch' doesn't contain any patch
dpkg-source: info: applying tests-egis0570-capture.pcapng-Remove-execution-permission.patch
Check disk space
----------------
Sufficient free space for build
User Environment
----------------
APT_CONFIG=/var/lib/sbuild/apt.conf
DEB_BUILD_OPTIONS=parallel=4
HOME=/sbuild-nonexistent
LC_ALL=POSIX
LOGNAME=buildd
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=trixie-staging-armhf-sbuild
SCHROOT_CHROOT_NAME=trixie-staging-armhf-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=112
SCHROOT_GROUP=buildd
SCHROOT_SESSION_ID=trixie-staging-armhf-sbuild-41cd2286-9212-4cec-8809-e0542a63639b
SCHROOT_UID=107
SCHROOT_USER=buildd
SHELL=/bin/sh
USER=buildd
dpkg-buildpackage
-----------------
dpkg-buildpackage: info: source package libfprint
dpkg-buildpackage: info: source version 1:1.94.6-2
dpkg-buildpackage: info: source distribution unstable
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture armhf
fakeroot debian/rules clean
dh clean --with gir
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -rf tests/__pycache__
dh_auto_clean
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_clean
debian/rules build-arch
dh build-arch --with gir
dh_update_autotools_config -a
dh_autoreconf -a
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_configure -- -Dudev_hwdb=enabled -Dudev_hwdb_dir=/lib/udev/hwdb.d -Dudev_rules_dir=/lib/udev/rules.d -Ddrivers=all -Dgtk-examples=false
cd obj-arm-linux-gnueabihf && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/arm-linux-gnueabihf -Dpython.bytecompile=-1 -Dudev_hwdb=enabled -Dudev_hwdb_dir=/lib/udev/hwdb.d -Dudev_rules_dir=/lib/udev/rules.d -Ddrivers=all -Dgtk-examples=false
The Meson build system
Version: 1.2.1
Source dir: /<<PKGBUILDDIR>>
Build dir: /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf
Build type: native build
Project name: libfprint
Project version: 1.94.6
C compiler for the host machine: cc (gcc 12.2.0 "cc (Raspbian 12.2.0-14+rpi1) 12.2.0")
C linker for the host machine: cc ld.bfd 2.40
C++ compiler for the host machine: c++ (gcc 12.2.0 "c++ (Raspbian 12.2.0-14+rpi1) 12.2.0")
C++ linker for the host machine: c++ ld.bfd 2.40
Host machine cpu family: arm
Host machine cpu: armv8l
Compiler for C supports arguments -Wall: YES
Compiler for C supports arguments -Wcast-align: YES
Compiler for C supports arguments -Wformat-nonliteral: YES
Compiler for C supports arguments -Wformat-security: YES
Compiler for C supports arguments -Wformat=2: YES
Compiler for C supports arguments -Wignored-qualifiers: YES
Compiler for C supports arguments -Wlogical-op: YES
Compiler for C supports arguments -Wmissing-declarations: YES
Compiler for C supports arguments -Wmissing-format-attribute: YES
Compiler for C supports arguments -Wmissing-include-dirs: YES
Compiler for C supports arguments -Wmissing-noreturn: YES
Compiler for C supports arguments -Wpointer-arith: YES
Compiler for C supports arguments -Wshadow: YES
Compiler for C supports arguments -Wswitch-enum: YES
Compiler for C supports arguments -Wtype-limits: YES
Compiler for C supports arguments -Wundef: YES
Compiler for C supports arguments -Wunused: YES
Compiler for C supports arguments -Werror=address: YES
Compiler for C supports arguments -Werror=array-bounds: YES
Compiler for C supports arguments -Werror=empty-body: YES
Compiler for C supports arguments -Werror=init-self: YES
Compiler for C supports arguments -Werror=int-to-pointer-cast: YES
Compiler for C supports arguments -Werror=main: YES
Compiler for C supports arguments -Werror=missing-braces: YES
Compiler for C supports arguments -Werror=nonnull: YES
Compiler for C supports arguments -Werror=redundant-decls: YES
Compiler for C supports arguments -Werror=return-type: YES
Compiler for C supports arguments -Werror=sequence-point: YES
Compiler for C supports arguments -Werror=trigraphs: YES
Compiler for C supports arguments -Werror=write-strings: YES
Compiler for C supports arguments -fno-strict-aliasing: YES
Compiler for C supports arguments -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56: YES
Compiler for C supports arguments -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56: YES
Compiler for C supports arguments -D_GNU_SOURCE: YES
Compiler for C supports arguments -DG_LOG_DOMAIN="libfprint": YES
Compiler for C supports arguments -Wimplicit-function-declaration: YES
Compiler for C supports arguments -Wmissing-prototypes: YES
Compiler for C supports arguments -Wnested-externs: YES
Compiler for C supports arguments -Wold-style-definition: YES
Compiler for C supports arguments -Wstrict-prototypes: YES
Compiler for C supports arguments -Werror=implicit: YES
Compiler for C supports arguments -Werror=pointer-to-int-cast: YES
../meson.build:74: WARNING: Consider using the built-in warning_level option instead of using "-Wall".
../meson.build:75: WARNING: Consider using the built-in warning_level option instead of using "-Wall".
Found pkg-config: /usr/bin/pkg-config (1.8.1)
Run-time dependency glib-2.0 found: YES 2.74.6
Run-time dependency gio-unix-2.0 found: YES 2.74.6
Run-time dependency gobject-2.0 found: YES 2.74.6
Run-time dependency gusb found: YES 0.3.10
Library m found: YES
Run-time dependency cairo found: YES 1.16.0
Run-time dependency gobject-introspection-1.0 found: YES 1.74.0
Run-time dependency pixman-1 found: YES 0.42.2
Run-time dependency nss found: YES 3.87.1
Run-time dependency gudev-1.0 found: YES 237
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency udev found: NO (tried pkgconfig and cmake)
Program glib-mkenums found: YES (/usr/bin/glib-mkenums)
Program glib-mkenums found: YES (/usr/bin/glib-mkenums)
Program glib-mkenums found: YES (/usr/bin/glib-mkenums)
Program glib-mkenums found: YES (/usr/bin/glib-mkenums)
Configuring fpi-drivers.c with command
Compiler for C supports arguments -Wno-error=redundant-decls: YES
Compiler for C supports arguments -Wno-redundant-decls: YES
Compiler for C supports arguments -Wno-discarded-qualifiers: YES
Compiler for C supports arguments -Wno-array-bounds: YES
Compiler for C supports arguments -Wno-array-parameter: YES
Dependency gobject-introspection-1.0 found: YES 1.74.0 (cached)
Dependency gobject-introspection-1.0 found: YES 1.74.0 (cached)
Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner)
Dependency gobject-introspection-1.0 found: YES 1.74.0 (cached)
Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler)
Configuring config.h using configuration
Configuring gtkdocentities.ent using configuration
Dependency glib-2.0 found: YES 2.74.6 (cached)
../doc/meson.build:22: WARNING: Project targets '>= 0.56.0' but uses feature deprecated since '0.56.0': dependency.get_pkgconfig_variable. use dependency.get_variable(pkgconfig : ...) instead
Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan)
Program gtkdoc-scangobj found: YES (/usr/bin/gtkdoc-scangobj)
Program gtkdoc-mkdb found: YES (/usr/bin/gtkdoc-mkdb)
Program gtkdoc-mkhtml found: YES (/usr/bin/gtkdoc-mkhtml)
Program gtkdoc-fixxref found: YES (/usr/bin/gtkdoc-fixxref)
Program python3 found: YES (/usr/bin/python3)
Configuring create-driver-test.py using configuration
Program unittest_inspector.py found: YES (/<<PKGBUILDDIR>>/tests/unittest_inspector.py)
Program umockdev-test.py found: YES (/<<PKGBUILDDIR>>/tests/umockdev-test.py)
Configuring virtual-image.test using configuration
Configuring virtual-device.test using configuration
Configuring driver-aes2501.test using configuration
Configuring driver-aes3500.test using configuration
Configuring driver-elan.test using configuration
Configuring driver-elan-cobo.test using configuration
Configuring driver-elanmoc.test using configuration
Configuring driver-elanspi.test using configuration
Configuring driver-synaptics.test using configuration
Configuring driver-upektc_img.test using configuration
Configuring driver-upektc_img-tcs1s.test using configuration
Configuring driver-uru4000-msv2.test using configuration
Configuring driver-uru4000-4500.test using configuration
Configuring driver-vfs0050.test using configuration
Configuring driver-vfs301.test using configuration
Configuring driver-vfs5011.test using configuration
Configuring driver-vfs7552.test using configuration
Configuring driver-goodixmoc.test using configuration
Configuring driver-nb1010.test using configuration
Configuring driver-egis0570.test using configuration
Configuring driver-fpcmoc.test using configuration
Configuring fpi-device.test using configuration
Configuring fpi-ssm.test using configuration
Configuring fpi-assembling.test using configuration
Configuring fp-context.test using configuration
Configuring fp-device.test using configuration
Program test-generated-hwdb.sh found: YES (/<<PKGBUILDDIR>>/tests/test-generated-hwdb.sh)
Program gdb found: NO
Program valgrind found: NO
Build targets in project: 31
WARNING: Deprecated features used:
* 0.56.0: {'dependency.get_pkgconfig_variable'}
libfprint 1.94.6
Drivers
Drivers : upektc_img
vfs5011
vfs7552
aes3500
aes4000
aes1610
aes1660
aes2660
aes2501
aes2550
vfs101
vfs301
vfs0050
etes603
egis0570
vcom5s
synaptics
elan
elanmoc
uru4000
upektc
upeksonly
upekts
goodixmoc
nb1010
fpcmoc
elanspi
virtual_image
virtual_device
virtual_device_storage
User defined options
buildtype : plain
libdir : lib/arm-linux-gnueabihf
localstatedir : /var
prefix : /usr
sysconfdir : /etc
wrap_mode : nodownload
python.bytecompile: -1
drivers : all
gtk-examples : false
udev_hwdb : enabled
udev_hwdb_dir : /lib/udev/hwdb.d
udev_rules_dir : /lib/udev/rules.d
Found ninja-1.11.1 at /usr/bin/ninja
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build -a
cd obj-arm-linux-gnueabihf && LC_ALL=C.UTF-8 ninja -j4 -v
[1/141] /usr/bin/meson --internal exe --unpickle /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/meson-private/meson_exe_glib-mkenums_288d7ad53cdafa2ce96a564f15ed335a9eaa5ce4.dat
[2/141] /usr/bin/meson --internal exe --unpickle /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/meson-private/meson_exe_glib-mkenums_4c84f32ac58bea8b223390c1df444c88417814a6.dat
[3/141] /usr/bin/meson --internal exe --unpickle /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/meson-private/meson_exe_glib-mkenums_2bc39a346d3332c46530e95cb1bca9ab7f90f802.dat
[4/141] /usr/bin/meson --internal exe --unpickle /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/meson-private/meson_exe_glib-mkenums_f2352623455dde1d758066ab770e071612ee933f.dat
[5/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_bozorth3_bz_gbls.c.o -MF libfprint/libnbis.a.p/nbis_bozorth3_bz_gbls.c.o.d -o libfprint/libnbis.a.p/nbis_bozorth3_bz_gbls.c.o -c ../libfprint/nbis/bozorth3/bz_gbls.c
[6/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_bozorth3_bz_alloc.c.o -MF libfprint/libnbis.a.p/nbis_bozorth3_bz_alloc.c.o.d -o libfprint/libnbis.a.p/nbis_bozorth3_bz_alloc.c.o -c ../libfprint/nbis/bozorth3/bz_alloc.c
[7/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_bozorth3_bz_drvrs.c.o -MF libfprint/libnbis.a.p/nbis_bozorth3_bz_drvrs.c.o.d -o libfprint/libnbis.a.p/nbis_bozorth3_bz_drvrs.c.o -c ../libfprint/nbis/bozorth3/bz_drvrs.c
[8/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_bozorth3_bz_io.c.o -MF libfprint/libnbis.a.p/nbis_bozorth3_bz_io.c.o.d -o libfprint/libnbis.a.p/nbis_bozorth3_bz_io.c.o -c ../libfprint/nbis/bozorth3/bz_io.c
[9/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_bozorth3_bz_sort.c.o -MF libfprint/libnbis.a.p/nbis_bozorth3_bz_sort.c.o.d -o libfprint/libnbis.a.p/nbis_bozorth3_bz_sort.c.o -c ../libfprint/nbis/bozorth3/bz_sort.c
[10/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_binar.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_binar.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_binar.c.o -c ../libfprint/nbis/mindtct/binar.c
[11/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_chaincod.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_chaincod.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_chaincod.c.o -c ../libfprint/nbis/mindtct/chaincod.c
[12/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_block.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_block.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_block.c.o -c ../libfprint/nbis/mindtct/block.c
[13/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_detect.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_detect.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_detect.c.o -c ../libfprint/nbis/mindtct/detect.c
[14/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_dft.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_dft.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_dft.c.o -c ../libfprint/nbis/mindtct/dft.c
[15/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_bozorth3_bozorth3.c.o -MF libfprint/libnbis.a.p/nbis_bozorth3_bozorth3.c.o.d -o libfprint/libnbis.a.p/nbis_bozorth3_bozorth3.c.o -c ../libfprint/nbis/bozorth3/bozorth3.c
[16/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_free.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_free.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_free.c.o -c ../libfprint/nbis/mindtct/free.c
[17/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_contour.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_contour.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_contour.c.o -c ../libfprint/nbis/mindtct/contour.c
[18/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_getmin.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_getmin.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_getmin.c.o -c ../libfprint/nbis/mindtct/getmin.c
[19/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_globals.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_globals.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_globals.c.o -c ../libfprint/nbis/mindtct/globals.c
[20/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_init.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_init.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_init.c.o -c ../libfprint/nbis/mindtct/init.c
[21/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_imgutil.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_imgutil.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_imgutil.c.o -c ../libfprint/nbis/mindtct/imgutil.c
[22/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_line.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_line.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_line.c.o -c ../libfprint/nbis/mindtct/line.c
[23/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_link.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_link.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_link.c.o -c ../libfprint/nbis/mindtct/link.c
[24/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_log.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_log.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_log.c.o -c ../libfprint/nbis/mindtct/log.c
[25/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_matchpat.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_matchpat.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_matchpat.c.o -c ../libfprint/nbis/mindtct/matchpat.c
[26/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_loop.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_loop.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_loop.c.o -c ../libfprint/nbis/mindtct/loop.c
[27/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_morph.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_morph.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_morph.c.o -c ../libfprint/nbis/mindtct/morph.c
[28/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_maps.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_maps.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_maps.c.o -c ../libfprint/nbis/mindtct/maps.c
[29/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_minutia.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_minutia.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_minutia.c.o -c ../libfprint/nbis/mindtct/minutia.c
[30/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_quality.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_quality.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_quality.c.o -c ../libfprint/nbis/mindtct/quality.c
[31/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_shape.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_shape.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_shape.c.o -c ../libfprint/nbis/mindtct/shape.c
[32/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_sort.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_sort.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_sort.c.o -c ../libfprint/nbis/mindtct/sort.c
[33/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_ridges.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_ridges.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_ridges.c.o -c ../libfprint/nbis/mindtct/ridges.c
[34/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_util.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_util.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_util.c.o -c ../libfprint/nbis/mindtct/util.c
[35/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_xytreps.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_xytreps.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_xytreps.c.o -c ../libfprint/nbis/mindtct/xytreps.c
[36/141] cc -Ilibfprint/libnbis.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wno-error=redundant-decls -Wno-redundant-decls -Wno-discarded-qualifiers -Wno-array-bounds -Wno-array-parameter -MD -MQ libfprint/libnbis.a.p/nbis_mindtct_remove.c.o -MF libfprint/libnbis.a.p/nbis_mindtct_remove.c.o.d -o libfprint/libnbis.a.p/nbis_mindtct_remove.c.o -c ../libfprint/nbis/mindtct/remove.c
[37/141] rm -f libfprint/libnbis.a && gcc-ar csrDT libfprint/libnbis.a libfprint/libnbis.a.p/nbis_bozorth3_bozorth3.c.o libfprint/libnbis.a.p/nbis_bozorth3_bz_alloc.c.o libfprint/libnbis.a.p/nbis_bozorth3_bz_drvrs.c.o libfprint/libnbis.a.p/nbis_bozorth3_bz_gbls.c.o libfprint/libnbis.a.p/nbis_bozorth3_bz_io.c.o libfprint/libnbis.a.p/nbis_bozorth3_bz_sort.c.o libfprint/libnbis.a.p/nbis_mindtct_binar.c.o libfprint/libnbis.a.p/nbis_mindtct_block.c.o libfprint/libnbis.a.p/nbis_mindtct_chaincod.c.o libfprint/libnbis.a.p/nbis_mindtct_contour.c.o libfprint/libnbis.a.p/nbis_mindtct_detect.c.o libfprint/libnbis.a.p/nbis_mindtct_dft.c.o libfprint/libnbis.a.p/nbis_mindtct_free.c.o libfprint/libnbis.a.p/nbis_mindtct_getmin.c.o libfprint/libnbis.a.p/nbis_mindtct_globals.c.o libfprint/libnbis.a.p/nbis_mindtct_imgutil.c.o libfprint/libnbis.a.p/nbis_mindtct_init.c.o libfprint/libnbis.a.p/nbis_mindtct_line.c.o libfprint/libnbis.a.p/nbis_mindtct_link.c.o libfprint/libnbis.a.p/nbis_mindtct_log.c.o libfprint/libnbis.a.p/nbis_mindtct_loop.c.o libfprint/libnbis.a.p/nbis_mindtct_maps.c.o libfprint/libnbis.a.p/nbis_mindtct_matchpat.c.o libfprint/libnbis.a.p/nbis_mindtct_minutia.c.o libfprint/libnbis.a.p/nbis_mindtct_morph.c.o libfprint/libnbis.a.p/nbis_mindtct_quality.c.o libfprint/libnbis.a.p/nbis_mindtct_remove.c.o libfprint/libnbis.a.p/nbis_mindtct_ridges.c.o libfprint/libnbis.a.p/nbis_mindtct_shape.c.o libfprint/libnbis.a.p/nbis_mindtct_sort.c.o libfprint/libnbis.a.p/nbis_mindtct_util.c.o libfprint/libnbis.a.p/nbis_mindtct_xytreps.c.o
[38/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/meson-generated_.._fpi-enums.c.o -MF libfprint/libfprint-private.a.p/meson-generated_.._fpi-enums.c.o.d -o libfprint/libfprint-private.a.p/meson-generated_.._fpi-enums.c.o -c libfprint/fpi-enums.c
[39/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/fpi-assembling.c.o -MF libfprint/libfprint-private.a.p/fpi-assembling.c.o.d -o libfprint/libfprint-private.a.p/fpi-assembling.c.o -c ../libfprint/fpi-assembling.c
[40/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/fpi-image-device.c.o -MF libfprint/libfprint-private.a.p/fpi-image-device.c.o.d -o libfprint/libfprint-private.a.p/fpi-image-device.c.o -c ../libfprint/fpi-image-device.c
[41/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/fpi-byte-reader.c.o -MF libfprint/libfprint-private.a.p/fpi-byte-reader.c.o.d -o libfprint/libfprint-private.a.p/fpi-byte-reader.c.o -c ../libfprint/fpi-byte-reader.c
[42/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/fpi-byte-writer.c.o -MF libfprint/libfprint-private.a.p/fpi-byte-writer.c.o.d -o libfprint/libfprint-private.a.p/fpi-byte-writer.c.o -c ../libfprint/fpi-byte-writer.c
[43/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/fpi-device.c.o -MF libfprint/libfprint-private.a.p/fpi-device.c.o.d -o libfprint/libfprint-private.a.p/fpi-device.c.o -c ../libfprint/fpi-device.c
[44/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/fpi-image.c.o -MF libfprint/libfprint-private.a.p/fpi-image.c.o.d -o libfprint/libfprint-private.a.p/fpi-image.c.o -c ../libfprint/fpi-image.c
../libfprint/fpi-image.c: In function ‘fpi_image_resize’:
../libfprint/fpi-image.c:123:82: warning: cast increases required alignment of target type [-Wcast-align]
123 | orig = pixman_image_create_bits (PIXMAN_a8, orig_img->width, orig_img->height, (uint32_t *) orig_img->data, orig_img->width);
| ^
[45/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/fpi-ssm.c.o -MF libfprint/libfprint-private.a.p/fpi-ssm.c.o.d -o libfprint/libfprint-private.a.p/fpi-ssm.c.o -c ../libfprint/fpi-ssm.c
[46/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/fpi-print.c.o -MF libfprint/libfprint-private.a.p/fpi-print.c.o.d -o libfprint/libfprint-private.a.p/fpi-print.c.o -c ../libfprint/fpi-print.c
[47/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_upek_proto.c.o -MF libfprint/libfprint-drivers.a.p/drivers_upek_proto.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_upek_proto.c.o -c ../libfprint/drivers/upek_proto.c
[48/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/fpi-spi-transfer.c.o -MF libfprint/libfprint-private.a.p/fpi-spi-transfer.c.o.d -o libfprint/libfprint-private.a.p/fpi-spi-transfer.c.o -c ../libfprint/fpi-spi-transfer.c
[49/141] cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-private.a.p/fpi-usb-transfer.c.o -MF libfprint/libfprint-private.a.p/fpi-usb-transfer.c.o.d -o libfprint/libfprint-private.a.p/fpi-usb-transfer.c.o -c ../libfprint/fpi-usb-transfer.c
[50/141] rm -f libfprint/libfprint-private.a && gcc-ar csrDT libfprint/libfprint-private.a libfprint/libfprint-private.a.p/meson-generated_.._fpi-enums.c.o libfprint/libfprint-private.a.p/fpi-assembling.c.o libfprint/libfprint-private.a.p/fpi-byte-reader.c.o libfprint/libfprint-private.a.p/fpi-byte-writer.c.o libfprint/libfprint-private.a.p/fpi-device.c.o libfprint/libfprint-private.a.p/fpi-image-device.c.o libfprint/libfprint-private.a.p/fpi-image.c.o libfprint/libfprint-private.a.p/fpi-print.c.o libfprint/libfprint-private.a.p/fpi-ssm.c.o libfprint/libfprint-private.a.p/fpi-usb-transfer.c.o libfprint/libfprint-private.a.p/fpi-spi-transfer.c.o
[51/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_upektc_img.c.o -MF libfprint/libfprint-drivers.a.p/drivers_upektc_img.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_upektc_img.c.o -c ../libfprint/drivers/upektc_img.c
[52/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_aes3500.c.o -MF libfprint/libfprint-drivers.a.p/drivers_aes3500.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_aes3500.c.o -c ../libfprint/drivers/aes3500.c
[53/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_vfs5011.c.o -MF libfprint/libfprint-drivers.a.p/drivers_vfs5011.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_vfs5011.c.o -c ../libfprint/drivers/vfs5011.c
[54/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_aes4000.c.o -MF libfprint/libfprint-drivers.a.p/drivers_aes4000.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_aes4000.c.o -c ../libfprint/drivers/aes4000.c
[55/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_aes1660.c.o -MF libfprint/libfprint-drivers.a.p/drivers_aes1660.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_aes1660.c.o -c ../libfprint/drivers/aes1660.c
[56/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_vfs7552.c.o -MF libfprint/libfprint-drivers.a.p/drivers_vfs7552.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_vfs7552.c.o -c ../libfprint/drivers/vfs7552.c
[57/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_aes1610.c.o -MF libfprint/libfprint-drivers.a.p/drivers_aes1610.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_aes1610.c.o -c ../libfprint/drivers/aes1610.c
[58/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_aes2660.c.o -MF libfprint/libfprint-drivers.a.p/drivers_aes2660.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_aes2660.c.o -c ../libfprint/drivers/aes2660.c
[59/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_aes2501.c.o -MF libfprint/libfprint-drivers.a.p/drivers_aes2501.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_aes2501.c.o -c ../libfprint/drivers/aes2501.c
../libfprint/drivers/aes2501.c: In function ‘sum_histogram_values’:
../libfprint/drivers/aes2501.c:208:24: warning: cast increases required alignment of target type [-Wcast-align]
208 | guint16 *histogram = (guint16 *) (data + 1);
| ^
[60/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_aes2550.c.o -MF libfprint/libfprint-drivers.a.p/drivers_aes2550.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_aes2550.c.o -c ../libfprint/drivers/aes2550.c
[61/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_vfs301.c.o -MF libfprint/libfprint-drivers.a.p/drivers_vfs301.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_vfs301.c.o -c ../libfprint/drivers/vfs301.c
[62/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_vfs101.c.o -MF libfprint/libfprint-drivers.a.p/drivers_vfs101.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_vfs101.c.o -c ../libfprint/drivers/vfs101.c
[63/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_vfs0050.c.o -MF libfprint/libfprint-drivers.a.p/drivers_vfs0050.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_vfs0050.c.o -c ../libfprint/drivers/vfs0050.c
[64/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_vfs301_proto.c.o -MF libfprint/libfprint-drivers.a.p/drivers_vfs301_proto.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_vfs301_proto.c.o -c ../libfprint/drivers/vfs301_proto.c
[65/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_vcom5s.c.o -MF libfprint/libfprint-drivers.a.p/drivers_vcom5s.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_vcom5s.c.o -c ../libfprint/drivers/vcom5s.c
[66/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_etes603.c.o -MF libfprint/libfprint-drivers.a.p/drivers_etes603.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_etes603.c.o -c ../libfprint/drivers/etes603.c
[67/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_egis0570.c.o -MF libfprint/libfprint-drivers.a.p/drivers_egis0570.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_egis0570.c.o -c ../libfprint/drivers/egis0570.c
In file included from /usr/include/glib-2.0/glib.h:64,
from /usr/include/glib-2.0/gobject/gbinding.h:30,
from /usr/include/glib-2.0/glib-object.h:24,
from ../libfprint/fpi-compat.h:21,
from ../libfprint/drivers_api.h:24,
from ../libfprint/drivers/egis0570.c:24:
../libfprint/drivers/egis0570.c: In function ‘postprocess_frames’:
../libfprint/drivers/egis0570.c:127:15: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘size_t’ {aka ‘unsigned int’} [-Wformat=]
127 | fp_dbg ("Finger status (picture number, mean) : %ld , %ld", k, mean[k]);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~
| |
| size_t {aka unsigned int}
/usr/include/glib-2.0/glib/gmessages.h:362:32: note: in definition of macro ‘g_debug’
362 | __VA_ARGS__)
| ^~~~~~~~~~~
../libfprint/drivers/egis0570.c:127:7: note: in expansion of macro ‘fp_dbg’
127 | fp_dbg ("Finger status (picture number, mean) : %ld , %ld", k, mean[k]);
| ^~~~~~
../libfprint/drivers/egis0570.c:127:57: note: format string is defined here
127 | fp_dbg ("Finger status (picture number, mean) : %ld , %ld", k, mean[k]);
| ~~^
| |
| long int
| %d
../libfprint/drivers/egis0570.c:127:15: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘size_t’ {aka ‘unsigned int’} [-Wformat=]
127 | fp_dbg ("Finger status (picture number, mean) : %ld , %ld", k, mean[k]);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~
| |
| size_t {aka unsigned int}
/usr/include/glib-2.0/glib/gmessages.h:362:32: note: in definition of macro ‘g_debug’
362 | __VA_ARGS__)
| ^~~~~~~~~~~
../libfprint/drivers/egis0570.c:127:7: note: in expansion of macro ‘fp_dbg’
127 | fp_dbg ("Finger status (picture number, mean) : %ld , %ld", k, mean[k]);
| ^~~~~~
../libfprint/drivers/egis0570.c:127:63: note: format string is defined here
127 | fp_dbg ("Finger status (picture number, mean) : %ld , %ld", k, mean[k]);
| ~~^
| |
| long int
| %d
[68/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_synaptics_bmkt_message.c.o -MF libfprint/libfprint-drivers.a.p/drivers_synaptics_bmkt_message.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_synaptics_bmkt_message.c.o -c ../libfprint/drivers/synaptics/bmkt_message.c
[69/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_elan.c.o -MF libfprint/libfprint-drivers.a.p/drivers_elan.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_elan.c.o -c ../libfprint/drivers/elan.c
../libfprint/drivers/elan.c: In function ‘elan_save_frame’:
../libfprint/drivers/elan.c:149:12: warning: cast increases required alignment of target type [-Wcast-align]
149 | ((unsigned short *) self->last_read)[raw_idx];
| ^
[70/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_synaptics_synaptics.c.o -MF libfprint/libfprint-drivers.a.p/drivers_synaptics_synaptics.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_synaptics_synaptics.c.o -c ../libfprint/drivers/synaptics/synaptics.c
[71/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_elanmoc_elanmoc.c.o -MF libfprint/libfprint-drivers.a.p/drivers_elanmoc_elanmoc.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_elanmoc_elanmoc.c.o -c ../libfprint/drivers/elanmoc/elanmoc.c
[72/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_upektc.c.o -MF libfprint/libfprint-drivers.a.p/drivers_upektc.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_upektc.c.o -c ../libfprint/drivers/upektc.c
[73/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_uru4000.c.o -MF libfprint/libfprint-drivers.a.p/drivers_uru4000.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_uru4000.c.o -c ../libfprint/drivers/uru4000.c
In file included from /usr/include/glib-2.0/glib/galloca.h:34,
from /usr/include/glib-2.0/glib.h:32,
from /usr/include/glib-2.0/gobject/gbinding.h:30,
from /usr/include/glib-2.0/glib-object.h:24,
from ../libfprint/fpi-compat.h:21,
from ../libfprint/drivers_api.h:24,
from ../libfprint/drivers/uru4000.c:26:
../libfprint/drivers/uru4000.c: In function ‘irq_handler’:
../libfprint/drivers/uru4000.c:339:29: warning: cast increases required alignment of target type [-Wcast-align]
339 | type = GUINT16_FROM_BE (*((uint16_t *) data));
| ^
/usr/include/glib-2.0/glib/gtypes.h:215:27: note: in definition of macro ‘GUINT16_SWAP_LE_BE_CONSTANT’
215 | (guint16) ((guint16) (val) >> 8) | \
| ^~~
/usr/lib/arm-linux-gnueabihf/glib-2.0/include/glibconfig.h:156:34: note: in expansion of macro ‘GUINT16_SWAP_LE_BE’
156 | #define GUINT16_TO_BE(val) (GUINT16_SWAP_LE_BE (val))
| ^~~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/glib/gtypes.h:411:34: note: in expansion of macro ‘GUINT16_TO_BE’
411 | #define GUINT16_FROM_BE(val) (GUINT16_TO_BE (val))
| ^~~~~~~~~~~~~
../libfprint/drivers/uru4000.c:339:10: note: in expansion of macro ‘GUINT16_FROM_BE’
339 | type = GUINT16_FROM_BE (*((uint16_t *) data));
| ^~~~~~~~~~~~~~~
../libfprint/drivers/uru4000.c:339:29: warning: cast increases required alignment of target type [-Wcast-align]
339 | type = GUINT16_FROM_BE (*((uint16_t *) data));
| ^
/usr/include/glib-2.0/glib/gtypes.h:216:27: note: in definition of macro ‘GUINT16_SWAP_LE_BE_CONSTANT’
216 | (guint16) ((guint16) (val) << 8)))
| ^~~
/usr/lib/arm-linux-gnueabihf/glib-2.0/include/glibconfig.h:156:34: note: in expansion of macro ‘GUINT16_SWAP_LE_BE’
156 | #define GUINT16_TO_BE(val) (GUINT16_SWAP_LE_BE (val))
| ^~~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/glib/gtypes.h:411:34: note: in expansion of macro ‘GUINT16_TO_BE’
411 | #define GUINT16_FROM_BE(val) (GUINT16_TO_BE (val))
| ^~~~~~~~~~~~~
../libfprint/drivers/uru4000.c:339:10: note: in expansion of macro ‘GUINT16_FROM_BE’
339 | type = GUINT16_FROM_BE (*((uint16_t *) data));
| ^~~~~~~~~~~~~~~
[74/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_upeksonly.c.o -MF libfprint/libfprint-drivers.a.p/drivers_upeksonly.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_upeksonly.c.o -c ../libfprint/drivers/upeksonly.c
[75/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_upekts.c.o -MF libfprint/libfprint-drivers.a.p/drivers_upekts.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_upekts.c.o -c ../libfprint/drivers/upekts.c
[76/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_goodixmoc_goodix_proto.c.o -MF libfprint/libfprint-drivers.a.p/drivers_goodixmoc_goodix_proto.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_goodixmoc_goodix_proto.c.o -c ../libfprint/drivers/goodixmoc/goodix_proto.c
In file included from /usr/include/glib-2.0/glib/gtypes.h:34,
from /usr/include/glib-2.0/glib/galloca.h:34,
from /usr/include/glib-2.0/glib.h:32,
from ../libfprint/drivers/goodixmoc/goodix_proto.c:20:
../libfprint/drivers/goodixmoc/goodix_proto.c: In function ‘gx_proto_parse_body’:
../libfprint/drivers/goodixmoc/goodix_proto.c:366:49: warning: cast increases required alignment of target type [-Wcast-align]
366 | uint16_t tid_size = GUINT16_FROM_LE (*(uint16_t *) (buffer + 1));
| ^
/usr/lib/arm-linux-gnueabihf/glib-2.0/include/glibconfig.h:154:45: note: in definition of macro ‘GUINT16_TO_LE’
154 | #define GUINT16_TO_LE(val) ((guint16) (val))
| ^~~
../libfprint/drivers/goodixmoc/goodix_proto.c:366:31: note: in expansion of macro ‘GUINT16_FROM_LE’
366 | uint16_t tid_size = GUINT16_FROM_LE (*(uint16_t *) (buffer + 1));
| ^~~~~~~~~~~~~~~
../libfprint/drivers/goodixmoc/goodix_proto.c:388:47: warning: cast increases required alignment of target type [-Wcast-align]
388 | fingerid_length = GUINT16_FROM_LE (*(uint16_t *) (fingerlist + offset));
| ^
/usr/lib/arm-linux-gnueabihf/glib-2.0/include/glibconfig.h:154:45: note: in definition of macro ‘GUINT16_TO_LE’
154 | #define GUINT16_TO_LE(val) ((guint16) (val))
| ^~~
../libfprint/drivers/goodixmoc/goodix_proto.c:388:29: note: in expansion of macro ‘GUINT16_FROM_LE’
388 | fingerid_length = GUINT16_FROM_LE (*(uint16_t *) (fingerlist + offset));
| ^~~~~~~~~~~~~~~
../libfprint/drivers/goodixmoc/goodix_proto.c:414:60: warning: cast increases required alignment of target type [-Wcast-align]
414 | presp->verify.rejectdetail = GUINT16_FROM_LE (*(uint16_t *) (buffer + offset));
| ^
/usr/lib/arm-linux-gnueabihf/glib-2.0/include/glibconfig.h:154:45: note: in definition of macro ‘GUINT16_TO_LE’
154 | #define GUINT16_TO_LE(val) ((guint16) (val))
| ^~~
../libfprint/drivers/goodixmoc/goodix_proto.c:414:42: note: in expansion of macro ‘GUINT16_FROM_LE’
414 | presp->verify.rejectdetail = GUINT16_FROM_LE (*(uint16_t *) (buffer + offset));
| ^~~~~~~~~~~~~~~
../libfprint/drivers/goodixmoc/goodix_proto.c:416:39: warning: cast increases required alignment of target type [-Wcast-align]
416 | score = GUINT32_FROM_LE (*(uint32_t *) (buffer + offset));
| ^
/usr/lib/arm-linux-gnueabihf/glib-2.0/include/glibconfig.h:159:45: note: in definition of macro ‘GUINT32_TO_LE’
159 | #define GUINT32_TO_LE(val) ((guint32) (val))
| ^~~
../libfprint/drivers/goodixmoc/goodix_proto.c:416:21: note: in expansion of macro ‘GUINT32_FROM_LE’
416 | score = GUINT32_FROM_LE (*(uint32_t *) (buffer + offset));
| ^~~~~~~~~~~~~~~
../libfprint/drivers/goodixmoc/goodix_proto.c:420:47: warning: cast increases required alignment of target type [-Wcast-align]
420 | fingerid_size = GUINT16_FROM_LE (*(uint16_t *) (buffer + offset));
| ^
/usr/lib/arm-linux-gnueabihf/glib-2.0/include/glibconfig.h:154:45: note: in definition of macro ‘GUINT16_TO_LE’
154 | #define GUINT16_TO_LE(val) ((guint16) (val))
| ^~~
../libfprint/drivers/goodixmoc/goodix_proto.c:420:29: note: in expansion of macro ‘GUINT16_FROM_LE’
420 | fingerid_size = GUINT16_FROM_LE (*(uint16_t *) (buffer + offset));
| ^~~~~~~~~~~~~~~
[77/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_nb1010.c.o -MF libfprint/libfprint-drivers.a.p/drivers_nb1010.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_nb1010.c.o -c ../libfprint/drivers/nb1010.c
[78/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_goodixmoc_goodix.c.o -MF libfprint/libfprint-drivers.a.p/drivers_goodixmoc_goodix.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_goodixmoc_goodix.c.o -c ../libfprint/drivers/goodixmoc/goodix.c
In file included from /usr/include/glib-2.0/glib/gtypes.h:34,
from /usr/include/glib-2.0/glib/galloca.h:34,
from /usr/include/glib-2.0/glib.h:32,
from /usr/include/glib-2.0/gobject/gbinding.h:30,
from /usr/include/glib-2.0/glib-object.h:24,
from ../libfprint/fpi-compat.h:21,
from ../libfprint/drivers_api.h:24,
from ../libfprint/drivers/goodixmoc/goodix.c:24:
../libfprint/drivers/goodixmoc/goodix.c: In function ‘fp_cmd_receive_cb’:
../libfprint/drivers/goodixmoc/goodix.c:167:38: warning: cast increases required alignment of target type [-Wcast-align]
167 | if(crc32_calc != GUINT32_FROM_LE (*(uint32_t *) (transfer->buffer + PACKAGE_HEADER_SIZE + header.len)))
| ^
/usr/lib/arm-linux-gnueabihf/glib-2.0/include/glibconfig.h:159:45: note: in definition of macro ‘GUINT32_TO_LE’
159 | #define GUINT32_TO_LE(val) ((guint32) (val))
| ^~~
../libfprint/drivers/goodixmoc/goodix.c:167:20: note: in expansion of macro ‘GUINT32_FROM_LE’
167 | if(crc32_calc != GUINT32_FROM_LE (*(uint32_t *) (transfer->buffer + PACKAGE_HEADER_SIZE + header.len)))
| ^~~~~~~~~~~~~~~
[79/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_virtual-image.c.o -MF libfprint/libfprint-drivers.a.p/drivers_virtual-image.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_virtual-image.c.o -c ../libfprint/drivers/virtual-image.c
[80/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_fpcmoc_fpc.c.o -MF libfprint/libfprint-drivers.a.p/drivers_fpcmoc_fpc.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_fpcmoc_fpc.c.o -c ../libfprint/drivers/fpcmoc/fpc.c
In file included from /usr/include/glib-2.0/glib.h:64,
from /usr/include/glib-2.0/gobject/gbinding.h:30,
from /usr/include/glib-2.0/glib-object.h:24,
from ../libfprint/fpi-compat.h:21,
from ../libfprint/drivers_api.h:24,
from ../libfprint/drivers/fpcmoc/fpc.c:19:
../libfprint/drivers/fpcmoc/fpc.c: In function ‘fpc_cmd_receive_cb’:
../libfprint/drivers/fpcmoc/fpc.c:161:19: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘gssize’ {aka ‘int’} [-Wformat=]
161 | fp_dbg ("%s recv evt data length: %ld", G_STRFUNC, transfer->actual_length);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~
| |
| gssize {aka int}
/usr/include/glib-2.0/glib/gmessages.h:362:32: note: in definition of macro ‘g_debug’
362 | __VA_ARGS__)
| ^~~~~~~~~~~
../libfprint/drivers/fpcmoc/fpc.c:161:11: note: in expansion of macro ‘fp_dbg’
161 | fp_dbg ("%s recv evt data length: %ld", G_STRFUNC, transfer->actual_length);
| ^~~~~~
../libfprint/drivers/fpcmoc/fpc.c:161:47: note: format string is defined here
161 | fp_dbg ("%s recv evt data length: %ld", G_STRFUNC, transfer->actual_length);
| ~~^
| |
| long int
| %d
[81/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_virtual-device.c.o -MF libfprint/libfprint-drivers.a.p/drivers_virtual-device.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_virtual-device.c.o -c ../libfprint/drivers/virtual-device.c
[82/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_elanspi.c.o -MF libfprint/libfprint-drivers.a.p/drivers_elanspi.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_elanspi.c.o -c ../libfprint/drivers/elanspi.c
[83/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_virtual-device-storage.c.o -MF libfprint/libfprint-drivers.a.p/drivers_virtual-device-storage.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_virtual-device-storage.c.o -c ../libfprint/drivers/virtual-device-storage.c
[84/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_aeslib.c.o -MF libfprint/libfprint-drivers.a.p/drivers_aeslib.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_aeslib.c.o -c ../libfprint/drivers/aeslib.c
[85/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/meson-generated_.._fpi-drivers.c.o -MF libfprint/libfprint-drivers.a.p/meson-generated_.._fpi-drivers.c.o.d -o libfprint/libfprint-drivers.a.p/meson-generated_.._fpi-drivers.c.o -c libfprint/fpi-drivers.c
[86/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_aes3k.c.o -MF libfprint/libfprint-drivers.a.p/drivers_aes3k.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_aes3k.c.o -c ../libfprint/drivers/aes3k.c
[87/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_aesx660.c.o -MF libfprint/libfprint-drivers.a.p/drivers_aesx660.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_aesx660.c.o -c ../libfprint/drivers/aesx660.c
[88/141] cc -Ilibfprint/libfprint-drivers.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-drivers.a.p/drivers_virtual-device-listener.c.o -MF libfprint/libfprint-drivers.a.p/drivers_virtual-device-listener.c.o.d -o libfprint/libfprint-drivers.a.p/drivers_virtual-device-listener.c.o -c ../libfprint/drivers/virtual-device-listener.c
[89/141] rm -f libfprint/libfprint-drivers.a && gcc-ar csrDT libfprint/libfprint-drivers.a libfprint/libfprint-drivers.a.p/drivers_upektc_img.c.o libfprint/libfprint-drivers.a.p/drivers_upek_proto.c.o libfprint/libfprint-drivers.a.p/drivers_vfs5011.c.o libfprint/libfprint-drivers.a.p/drivers_vfs7552.c.o libfprint/libfprint-drivers.a.p/drivers_aes3500.c.o libfprint/libfprint-drivers.a.p/drivers_aes4000.c.o libfprint/libfprint-drivers.a.p/drivers_aes1610.c.o libfprint/libfprint-drivers.a.p/drivers_aes1660.c.o libfprint/libfprint-drivers.a.p/drivers_aes2660.c.o libfprint/libfprint-drivers.a.p/drivers_aes2501.c.o libfprint/libfprint-drivers.a.p/drivers_aes2550.c.o libfprint/libfprint-drivers.a.p/drivers_vfs101.c.o libfprint/libfprint-drivers.a.p/drivers_vfs301.c.o libfprint/libfprint-drivers.a.p/drivers_vfs301_proto.c.o libfprint/libfprint-drivers.a.p/drivers_vfs0050.c.o libfprint/libfprint-drivers.a.p/drivers_etes603.c.o libfprint/libfprint-drivers.a.p/drivers_egis0570.c.o libfprint/libfprint-drivers.a.p/drivers_vcom5s.c.o libfprint/libfprint-drivers.a.p/drivers_synaptics_synaptics.c.o libfprint/libfprint-drivers.a.p/drivers_synaptics_bmkt_message.c.o libfprint/libfprint-drivers.a.p/drivers_elan.c.o libfprint/libfprint-drivers.a.p/drivers_elanmoc_elanmoc.c.o libfprint/libfprint-drivers.a.p/drivers_uru4000.c.o libfprint/libfprint-drivers.a.p/drivers_upektc.c.o libfprint/libfprint-drivers.a.p/drivers_upeksonly.c.o libfprint/libfprint-drivers.a.p/drivers_upekts.c.o libfprint/libfprint-drivers.a.p/drivers_goodixmoc_goodix.c.o libfprint/libfprint-drivers.a.p/drivers_goodixmoc_goodix_proto.c.o libfprint/libfprint-drivers.a.p/drivers_nb1010.c.o libfprint/libfprint-drivers.a.p/drivers_fpcmoc_fpc.c.o libfprint/libfprint-drivers.a.p/drivers_elanspi.c.o libfprint/libfprint-drivers.a.p/drivers_virtual-image.c.o libfprint/libfprint-drivers.a.p/drivers_virtual-device.c.o libfprint/libfprint-drivers.a.p/drivers_virtual-device-storage.c.o libfprint/libfprint-drivers.a.p/drivers_aeslib.c.o libfprint/libfprint-drivers.a.p/drivers_aes3k.c.o libfprint/libfprint-drivers.a.p/drivers_aesx660.c.o libfprint/libfprint-drivers.a.p/drivers_virtual-device-listener.c.o libfprint/libfprint-drivers.a.p/meson-generated_.._fpi-drivers.c.o
[90/141] cc -Ilibfprint/libfprint-2.so.2.0.0.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-2.so.2.0.0.p/meson-generated_.._fp-enums.c.o -MF libfprint/libfprint-2.so.2.0.0.p/meson-generated_.._fp-enums.c.o.d -o libfprint/libfprint-2.so.2.0.0.p/meson-generated_.._fp-enums.c.o -c libfprint/fp-enums.c
[91/141] cc -Ilibfprint/libfprint-2.so.2.0.0.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-2.so.2.0.0.p/fp-context.c.o -MF libfprint/libfprint-2.so.2.0.0.p/fp-context.c.o.d -o libfprint/libfprint-2.so.2.0.0.p/fp-context.c.o -c ../libfprint/fp-context.c
[92/141] cc -Ilibfprint/libfprint-2.so.2.0.0.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-2.so.2.0.0.p/fp-image.c.o -MF libfprint/libfprint-2.so.2.0.0.p/fp-image.c.o.d -o libfprint/libfprint-2.so.2.0.0.p/fp-image.c.o -c ../libfprint/fp-image.c
../libfprint/fp-image.c: In function ‘fp_image_finalize’:
../libfprint/fp-image.c:62:19: warning: cast increases required alignment of target type [-Wcast-align]
62 | FpImage *self = (FpImage *) object;
| ^
../libfprint/fp-image.c: In function ‘fp_image_constructed’:
../libfprint/fp-image.c:74:19: warning: cast increases required alignment of target type [-Wcast-align]
74 | FpImage *self = (FpImage *) object;
| ^
[93/141] cc -Ilibfprint/libfprint-2.so.2.0.0.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-2.so.2.0.0.p/fp-image-device.c.o -MF libfprint/libfprint-2.so.2.0.0.p/fp-image-device.c.o.d -o libfprint/libfprint-2.so.2.0.0.p/fp-image-device.c.o -c ../libfprint/fp-image-device.c
[94/141] cc -Ilibfprint/libfprint-2.so.2.0.0.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-2.so.2.0.0.p/fp-print.c.o -MF libfprint/libfprint-2.so.2.0.0.p/fp-print.c.o.d -o libfprint/libfprint-2.so.2.0.0.p/fp-print.c.o -c ../libfprint/fp-print.c
[95/141] cc -Ilibfprint/libfprint-2.so.2.0.0.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ libfprint/libfprint-2.so.2.0.0.p/fp-device.c.o -MF libfprint/libfprint-2.so.2.0.0.p/fp-device.c.o.d -o libfprint/libfprint-2.so.2.0.0.p/fp-device.c.o -c ../libfprint/fp-device.c
[96/141] cc -Ilibfprint/fprint-list-udev-hwdb.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ libfprint/fprint-list-udev-hwdb.p/fprint-list-udev-hwdb.c.o -MF libfprint/fprint-list-udev-hwdb.p/fprint-list-udev-hwdb.c.o.d -o libfprint/fprint-list-udev-hwdb.p/fprint-list-udev-hwdb.c.o -c ../libfprint/fprint-list-udev-hwdb.c
[97/141] cc -Ilibfprint/fprint-list-udev-rules.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ libfprint/fprint-list-udev-rules.p/fprint-list-udev-rules.c.o -MF libfprint/fprint-list-udev-rules.p/fprint-list-udev-rules.c.o.d -o libfprint/fprint-list-udev-rules.p/fprint-list-udev-rules.c.o -c ../libfprint/fprint-list-udev-rules.c
[98/141] cc -o libfprint/libfprint-2.so.2.0.0 libfprint/libfprint-2.so.2.0.0.p/meson-generated_.._fp-enums.c.o libfprint/libfprint-2.so.2.0.0.p/fp-context.c.o libfprint/libfprint-2.so.2.0.0.p/fp-device.c.o libfprint/libfprint-2.so.2.0.0.p/fp-image.c.o libfprint/libfprint-2.so.2.0.0.p/fp-print.c.o libfprint/libfprint-2.so.2.0.0.p/fp-image-device.c.o -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,libfprint-2.so.2 -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 libfprint/libfprint-drivers.a libfprint/libfprint-private.a libfprint/libnbis.a -Wl,--version-script,/<<PKGBUILDDIR>>/libfprint/libfprint.ver /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -lm /usr/lib/arm-linux-gnueabihf/libpixman-1.so /usr/lib/arm-linux-gnueabihf/libnss3.so /usr/lib/arm-linux-gnueabihf/libnssutil3.so /usr/lib/arm-linux-gnueabihf/libsmime3.so /usr/lib/arm-linux-gnueabihf/libssl3.so /usr/lib/arm-linux-gnueabihf/libplds4.so /usr/lib/arm-linux-gnueabihf/libplc4.so /usr/lib/arm-linux-gnueabihf/libnspr4.so /usr/lib/arm-linux-gnueabihf/libgudev-1.0.so -Wl,--end-group
[99/141] cc -Ilibfprint/fprint-list-supported-devices.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ libfprint/fprint-list-supported-devices.p/fprint-list-supported-devices.c.o -MF libfprint/fprint-list-supported-devices.p/fprint-list-supported-devices.c.o.d -o libfprint/fprint-list-supported-devices.p/fprint-list-supported-devices.c.o -c ../libfprint/fprint-list-supported-devices.c
[100/141] /usr/bin/meson --internal symbolextractor /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf libfprint/libfprint-2.so.2.0.0 libfprint/libfprint-2.so.2.0.0 libfprint/libfprint-2.so.2.0.0.p/libfprint-2.so.2.0.0.symbols
[101/141] cc -Itests/libfprint-test-utils.a.p -Itests -I../tests -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ tests/libfprint-test-utils.a.p/test-utils.c.o -MF tests/libfprint-test-utils.a.p/test-utils.c.o.d -o tests/libfprint-test-utils.a.p/test-utils.c.o -c ../tests/test-utils.c
[102/141] cc -o libfprint/fprint-list-udev-rules libfprint/fprint-list-udev-rules.p/fprint-list-udev-rules.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint -Wl,--start-group libfprint/libfprint-drivers.a libfprint/libfprint-private.a libfprint/libnbis.a libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -lm /usr/lib/arm-linux-gnueabihf/libpixman-1.so /usr/lib/arm-linux-gnueabihf/libnss3.so /usr/lib/arm-linux-gnueabihf/libnssutil3.so /usr/lib/arm-linux-gnueabihf/libsmime3.so /usr/lib/arm-linux-gnueabihf/libssl3.so /usr/lib/arm-linux-gnueabihf/libplds4.so /usr/lib/arm-linux-gnueabihf/libplc4.so /usr/lib/arm-linux-gnueabihf/libnspr4.so /usr/lib/arm-linux-gnueabihf/libgudev-1.0.so -Wl,--end-group
[103/141] cc -o libfprint/fprint-list-udev-hwdb libfprint/fprint-list-udev-hwdb.p/fprint-list-udev-hwdb.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint -Wl,--start-group libfprint/libfprint-drivers.a libfprint/libfprint-private.a libfprint/libnbis.a libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -lm /usr/lib/arm-linux-gnueabihf/libpixman-1.so /usr/lib/arm-linux-gnueabihf/libnss3.so /usr/lib/arm-linux-gnueabihf/libnssutil3.so /usr/lib/arm-linux-gnueabihf/libsmime3.so /usr/lib/arm-linux-gnueabihf/libssl3.so /usr/lib/arm-linux-gnueabihf/libplds4.so /usr/lib/arm-linux-gnueabihf/libplc4.so /usr/lib/arm-linux-gnueabihf/libnspr4.so /usr/lib/arm-linux-gnueabihf/libgudev-1.0.so -Wl,--end-group
[104/141] /usr/bin/meson --internal exe --capture libfprint/70-libfprint-2.rules -- /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-rules
[105/141] cc -Itests/libfprint-test-utils.a.p -Itests -I../tests -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ tests/libfprint-test-utils.a.p/test-device-fake.c.o -MF tests/libfprint-test-utils.a.p/test-device-fake.c.o.d -o tests/libfprint-test-utils.a.p/test-device-fake.c.o -c ../tests/test-device-fake.c
[106/141] rm -f tests/libfprint-test-utils.a && gcc-ar csrDT tests/libfprint-test-utils.a tests/libfprint-test-utils.a.p/test-utils.c.o tests/libfprint-test-utils.a.p/test-device-fake.c.o
[107/141] cc -o libfprint/fprint-list-supported-devices libfprint/fprint-list-supported-devices.p/fprint-list-supported-devices.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint -Wl,--start-group libfprint/libfprint-drivers.a libfprint/libfprint-private.a libfprint/libnbis.a libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -lm /usr/lib/arm-linux-gnueabihf/libpixman-1.so /usr/lib/arm-linux-gnueabihf/libnss3.so /usr/lib/arm-linux-gnueabihf/libnssutil3.so /usr/lib/arm-linux-gnueabihf/libsmime3.so /usr/lib/arm-linux-gnueabihf/libssl3.so /usr/lib/arm-linux-gnueabihf/libplds4.so /usr/lib/arm-linux-gnueabihf/libplc4.so /usr/lib/arm-linux-gnueabihf/libnspr4.so /usr/lib/arm-linux-gnueabihf/libgudev-1.0.so -Wl,--end-group
[108/141] cc -Itests/test-fpi-assembling.p -Itests -I../tests -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/libpng16 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -MD -MQ tests/test-fpi-assembling.p/test-fpi-assembling.c.o -MF tests/test-fpi-assembling.p/test-fpi-assembling.c.o.d -o tests/test-fpi-assembling.p/test-fpi-assembling.c.o -c ../tests/test-fpi-assembling.c
[109/141] cc -o tests/test-fpi-assembling tests/test-fpi-assembling.p/test-fpi-assembling.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,--whole-archive -Wl,--start-group tests/libfprint-test-utils.a -Wl,--no-whole-archive -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint libfprint/libfprint-private.a libfprint/libnbis.a libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -lm /usr/lib/arm-linux-gnueabihf/libpixman-1.so /usr/lib/arm-linux-gnueabihf/libnss3.so /usr/lib/arm-linux-gnueabihf/libnssutil3.so /usr/lib/arm-linux-gnueabihf/libsmime3.so /usr/lib/arm-linux-gnueabihf/libssl3.so /usr/lib/arm-linux-gnueabihf/libplds4.so /usr/lib/arm-linux-gnueabihf/libplc4.so /usr/lib/arm-linux-gnueabihf/libnspr4.so /usr/lib/arm-linux-gnueabihf/libgudev-1.0.so /usr/lib/arm-linux-gnueabihf/libcairo.so -Wl,--end-group
[110/141] cc -Itests/test-fp-context.p -Itests -I../tests -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -MD -MQ tests/test-fp-context.p/test-fp-context.c.o -MF tests/test-fp-context.p/test-fp-context.c.o.d -o tests/test-fp-context.p/test-fp-context.c.o -c ../tests/test-fp-context.c
[111/141] cc -o tests/test-fp-context tests/test-fp-context.p/test-fp-context.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,--whole-archive -Wl,--start-group tests/libfprint-test-utils.a -Wl,--no-whole-archive -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint libfprint/libfprint-private.a libfprint/libnbis.a libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -lm /usr/lib/arm-linux-gnueabihf/libpixman-1.so /usr/lib/arm-linux-gnueabihf/libnss3.so /usr/lib/arm-linux-gnueabihf/libnssutil3.so /usr/lib/arm-linux-gnueabihf/libsmime3.so /usr/lib/arm-linux-gnueabihf/libssl3.so /usr/lib/arm-linux-gnueabihf/libplds4.so /usr/lib/arm-linux-gnueabihf/libplc4.so /usr/lib/arm-linux-gnueabihf/libnspr4.so /usr/lib/arm-linux-gnueabihf/libgudev-1.0.so -Wl,--end-group
[112/141] cc -Itests/test-fpi-ssm.p -Itests -I../tests -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -MD -MQ tests/test-fpi-ssm.p/test-fpi-ssm.c.o -MF tests/test-fpi-ssm.p/test-fpi-ssm.c.o.d -o tests/test-fpi-ssm.p/test-fpi-ssm.c.o -c ../tests/test-fpi-ssm.c
[113/141] cc -o tests/test-fpi-ssm tests/test-fpi-ssm.p/test-fpi-ssm.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,--whole-archive -Wl,--start-group tests/libfprint-test-utils.a -Wl,--no-whole-archive -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint libfprint/libfprint-private.a libfprint/libnbis.a libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -lm /usr/lib/arm-linux-gnueabihf/libpixman-1.so /usr/lib/arm-linux-gnueabihf/libnss3.so /usr/lib/arm-linux-gnueabihf/libnssutil3.so /usr/lib/arm-linux-gnueabihf/libsmime3.so /usr/lib/arm-linux-gnueabihf/libssl3.so /usr/lib/arm-linux-gnueabihf/libplds4.so /usr/lib/arm-linux-gnueabihf/libplc4.so /usr/lib/arm-linux-gnueabihf/libnspr4.so /usr/lib/arm-linux-gnueabihf/libgudev-1.0.so -Wl,--end-group
[114/141] cc -Itests/test-fp-device.p -Itests -I../tests -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -MD -MQ tests/test-fp-device.p/test-fp-device.c.o -MF tests/test-fp-device.p/test-fp-device.c.o.d -o tests/test-fp-device.p/test-fp-device.c.o -c ../tests/test-fp-device.c
[115/141] cc -o tests/test-fp-device tests/test-fp-device.p/test-fp-device.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,--whole-archive -Wl,--start-group tests/libfprint-test-utils.a -Wl,--no-whole-archive -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint libfprint/libfprint-private.a libfprint/libnbis.a libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -lm /usr/lib/arm-linux-gnueabihf/libpixman-1.so /usr/lib/arm-linux-gnueabihf/libnss3.so /usr/lib/arm-linux-gnueabihf/libnssutil3.so /usr/lib/arm-linux-gnueabihf/libsmime3.so /usr/lib/arm-linux-gnueabihf/libssl3.so /usr/lib/arm-linux-gnueabihf/libplds4.so /usr/lib/arm-linux-gnueabihf/libplc4.so /usr/lib/arm-linux-gnueabihf/libnspr4.so /usr/lib/arm-linux-gnueabihf/libgudev-1.0.so -Wl,--end-group
[116/141] cc -Iexamples/enroll.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/enroll.p/enroll.c.o -MF examples/enroll.p/enroll.c.o.d -o examples/enroll.p/enroll.c.o -c ../examples/enroll.c
[117/141] env PKG_CONFIG_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/meson-uninstalled CC=cc /usr/bin/g-ir-scanner --quiet --no-libtool --namespace=FPrint --nsversion=2.0 --warn-all --output libfprint/FPrint-2.0.gir --c-include=fprint.h -I/<<PKGBUILDDIR>>/libfprint -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint -I/<<PKGBUILDDIR>>/. -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/. -I/<<PKGBUILDDIR>>/libfprint/nbis/include -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/nbis/include -I/<<PKGBUILDDIR>>/libfprint/nbis/libfprint-include -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/nbis/libfprint-include --filelist=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/libfprint-2.so.2.0.0.p/FPrint_2.0_gir_filelist -L/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint --extra-library=fprint-2 --include=Gio-2.0 --include=GObject-2.0 --include=GUsb-1.0 --symbol-prefix=fp_ --identifier-prefix=Fp --pkg-export=fprint --cflags-begin -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -I/<<PKGBUILDDIR>>/. -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/. -I/<<PKGBUILDDIR>>/libfprint/nbis/include -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/nbis/include -I/<<PKGBUILDDIR>>/libfprint/nbis/libfprint-include -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -I/usr/include/gobject-introspection-1.0 --cflags-end --add-include-path=/usr/share/gir-1.0 -L/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint --library fprint-2 --extra-library=gio-2.0 --extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=gusb --extra-library=usb-1.0 --extra-library=m --extra-library=pixman-1 --extra-library=nss3 --extra-library=nssutil3 --extra-library=smime3 --extra-library=ssl3 --extra-library=plds4 --extra-library=plc4 --extra-library=nspr4 --extra-library=gudev-1.0 --extra-library=girepository-1.0 --sources-top-dirs /<<PKGBUILDDIR>>/ --sources-top-dirs /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/
[118/141] cc -Iexamples/enroll.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/enroll.p/storage.c.o -MF examples/enroll.p/storage.c.o.d -o examples/enroll.p/storage.c.o -c ../examples/storage.c
[119/141] cc -Iexamples/enroll.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/enroll.p/utilities.c.o -MF examples/enroll.p/utilities.c.o.d -o examples/enroll.p/utilities.c.o -c ../examples/utilities.c
[120/141] cc -o examples/enroll examples/enroll.p/enroll.c.o examples/enroll.p/storage.c.o examples/enroll.p/utilities.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint -Wl,--start-group libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -Wl,--end-group
[121/141] cc -Itests/test-fpi-device.p -Itests -I../tests -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/pixman-1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/gudev-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -MD -MQ tests/test-fpi-device.p/test-fpi-device.c.o -MF tests/test-fpi-device.p/test-fpi-device.c.o.d -o tests/test-fpi-device.p/test-fpi-device.c.o -c ../tests/test-fpi-device.c
[122/141] cc -Iexamples/identify.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/identify.p/identify.c.o -MF examples/identify.p/identify.c.o.d -o examples/identify.p/identify.c.o -c ../examples/identify.c
[123/141] /usr/bin/g-ir-compiler libfprint/FPrint-2.0.gir --output libfprint/FPrint-2.0.typelib --includedir=/usr/share/gir-1.0
[124/141] cc -o tests/test-fpi-device tests/test-fpi-device.p/test-fpi-device.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,--whole-archive -Wl,--start-group tests/libfprint-test-utils.a -Wl,--no-whole-archive -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint libfprint/libfprint-private.a libfprint/libnbis.a libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -lm /usr/lib/arm-linux-gnueabihf/libpixman-1.so /usr/lib/arm-linux-gnueabihf/libnss3.so /usr/lib/arm-linux-gnueabihf/libnssutil3.so /usr/lib/arm-linux-gnueabihf/libsmime3.so /usr/lib/arm-linux-gnueabihf/libssl3.so /usr/lib/arm-linux-gnueabihf/libplds4.so /usr/lib/arm-linux-gnueabihf/libplc4.so /usr/lib/arm-linux-gnueabihf/libnspr4.so /usr/lib/arm-linux-gnueabihf/libgudev-1.0.so -Wl,--end-group
[125/141] cc -Iexamples/identify.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/identify.p/storage.c.o -MF examples/identify.p/storage.c.o.d -o examples/identify.p/storage.c.o -c ../examples/storage.c
[126/141] cc -Iexamples/identify.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/identify.p/utilities.c.o -MF examples/identify.p/utilities.c.o.d -o examples/identify.p/utilities.c.o -c ../examples/utilities.c
[127/141] cc -o examples/identify examples/identify.p/identify.c.o examples/identify.p/storage.c.o examples/identify.p/utilities.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint -Wl,--start-group libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -Wl,--end-group
[128/141] cc -Iexamples/img-capture.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/img-capture.p/utilities.c.o -MF examples/img-capture.p/utilities.c.o.d -o examples/img-capture.p/utilities.c.o -c ../examples/utilities.c
[129/141] cc -Iexamples/img-capture.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/img-capture.p/img-capture.c.o -MF examples/img-capture.p/img-capture.c.o.d -o examples/img-capture.p/img-capture.c.o -c ../examples/img-capture.c
[130/141] cc -Iexamples/img-capture.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/img-capture.p/storage.c.o -MF examples/img-capture.p/storage.c.o.d -o examples/img-capture.p/storage.c.o -c ../examples/storage.c
[131/141] cc -o examples/img-capture examples/img-capture.p/img-capture.c.o examples/img-capture.p/storage.c.o examples/img-capture.p/utilities.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint -Wl,--start-group libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -Wl,--end-group
[132/141] cc -Iexamples/manage-prints.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/manage-prints.p/storage.c.o -MF examples/manage-prints.p/storage.c.o.d -o examples/manage-prints.p/storage.c.o -c ../examples/storage.c
[133/141] cc -Iexamples/manage-prints.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/manage-prints.p/utilities.c.o -MF examples/manage-prints.p/utilities.c.o.d -o examples/manage-prints.p/utilities.c.o -c ../examples/utilities.c
[134/141] cc -Iexamples/manage-prints.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/manage-prints.p/manage-prints.c.o -MF examples/manage-prints.p/manage-prints.c.o.d -o examples/manage-prints.p/manage-prints.c.o -c ../examples/manage-prints.c
[135/141] cc -o examples/manage-prints examples/manage-prints.p/manage-prints.c.o examples/manage-prints.p/storage.c.o examples/manage-prints.p/utilities.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint -Wl,--start-group libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -Wl,--end-group
[136/141] cc -Iexamples/verify.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/verify.p/storage.c.o -MF examples/verify.p/storage.c.o.d -o examples/verify.p/storage.c.o -c ../examples/storage.c
[137/141] cc -Iexamples/verify.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/verify.p/utilities.c.o -MF examples/verify.p/utilities.c.o.d -o examples/verify.p/utilities.c.o -c ../examples/utilities.c
[138/141] cc -Iexamples/verify.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/verify.p/verify.c.o -MF examples/verify.p/verify.c.o.d -o examples/verify.p/verify.c.o -c ../examples/verify.c
[139/141] cc -o examples/verify examples/verify.p/verify.c.o examples/verify.p/storage.c.o examples/verify.p/utilities.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint -Wl,--start-group libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -Wl,--end-group
[140/141] c++ -Iexamples/cpp-test.p -Iexamples -I../examples -I. -I.. -Ilibfprint -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MQ examples/cpp-test.p/cpp-test.cpp.o -MF examples/cpp-test.p/cpp-test.cpp.o.d -o examples/cpp-test.p/cpp-test.cpp.o -c ../examples/cpp-test.cpp
[141/141] c++ -o examples/cpp-test examples/cpp-test.p/cpp-test.cpp.o -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 '-Wl,-rpath,$ORIGIN/../libfprint' -Wl,-rpath-link,/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint -Wl,--start-group libfprint/libfprint-2.so.2.0.0 /usr/lib/arm-linux-gnueabihf/libgio-2.0.so /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /usr/lib/arm-linux-gnueabihf/libgusb.so /usr/lib/arm-linux-gnueabihf/libusb-1.0.so -Wl,--end-group
debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_test -- -C /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf --timeout-multiplier 5
cd obj-arm-linux-gnueabihf && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test -C /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf --timeout-multiplier 5
ninja: Entering directory `/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf'
ninja: no work to do.
1/116 libfprint:virtual-driver+virtual-image+VirtualImage / VirtualImage.test_capture_prevents_close OK 1.13s
2/116 libfprint:virtual-driver+virtual-image+VirtualImage / VirtualImage.test_features OK 1.12s
3/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_capture_unsupported OK 0.80s
4/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_change_enroll_stages OK 0.74s
5/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_change_scan_type OK 0.95s
6/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_close_error OK 0.90s
7/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_close_while_opening OK 1.24s
8/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_delayed_open OK 1.13s
9/116 libfprint:virtual-driver+virtual-image+VirtualImage / VirtualImage.test_verify_serialized OK 6.52s
10/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_delayed_open_with_keep_alive OK 1.31s
11/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_device_features OK 0.87s
12/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_device_properties OK 0.70s
13/116 libfprint:virtual-driver+virtual-image+VirtualImage / VirtualImage.test_identify OK 9.42s
14/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_device_sleep OK 1.52s
15/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_device_sleep_before_completing_verify OK 1.57s
16/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll OK 0.62s
17/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_script OK 0.85s
18/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_script_interactive OK 0.80s
19/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_device_sleep_on_cancellation OK 2.10s
20/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_verify_match OK 0.78s
21/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_verify_no_match OK 0.72s
22/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_verify_error OK 0.92s
23/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_verify_retry OK 0.89s
24/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_with_retry OK 0.90s
25/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_verify_script OK 1.03s
26/116 libfprint:virtual-driver+virtual-image+VirtualImage / VirtualImage.test_enroll_verify OK 13.65s
27/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_finger_status OK 0.95s
28/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_finger_status_after_sleep OK 0.91s
29/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_identify_unsupported OK 0.83s
30/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_open_error OK 0.97s
31/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_open_error_with_keep_alive OK 0.63s
32/116 libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_quick_enroll OK 0.97s
33/116 libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_capture OK 1.08s
34/116 libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_close OK 0.82s
35/116 libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_delete_print OK 1.11s
36/116 libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_enroll OK 1.08s
37/116 libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_identify OK 1.08s
38/116 libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_list_prints OK 1.15s
39/116 libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_capture OK 0.56s
40/116 libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_open OK 1.24s
41/116 libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_verify OK 1.16s
42/116 libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_close OK 0.91s
43/116 libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_delete_print OK 0.90s
44/116 libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_enroll OK 0.87s
45/116 libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_identify OK 0.85s
46/116 libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_list_prints OK 0.80s
47/116 libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_verify OK 0.85s
48/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_change_scan_type OK 0.54s
49/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_capture_unsupported OK 0.91s
50/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_change_enroll_stages OK 0.97s
51/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_close_error OK 0.82s
52/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_clear_storage_error OK 1.13s
53/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_clear_storage OK 1.76s
54/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_close_while_opening OK 1.32s
55/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_delayed_open OK 1.18s
56/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_delayed_open_with_keep_alive OK 1.08s
57/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_delete_error OK 0.89s
58/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_device_features OK 0.65s
59/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_device_properties OK 0.52s
60/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_delete_multiple_times OK 1.73s
61/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_device_sleep OK 1.30s
62/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_duplicate_enroll OK 0.87s
63/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_device_sleep_before_completing_verify OK 1.57s
64/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll OK 0.64s
65/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_device_sleep_on_cancellation OK 2.20s
66/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_script_interactive OK 0.80s
67/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_script OK 0.94s
68/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_verify_error OK 1.08s
69/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_verify_retry OK 0.65s
70/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_verify_no_match OK 0.87s
71/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_verify_match OK 1.07s
72/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_finger_status OK 0.59s
73/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_verify_script OK 1.24s
74/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_with_retry OK 0.89s
75/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_finger_status_after_sleep OK 0.96s
76/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_identify_no_match OK 0.84s
77/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_identify_match OK 1.11s
78/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_identify_missing_print OK 0.96s
79/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_identify_retry OK 0.86s
80/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_identify_unsupported OK 0.83s
81/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_list_delete_missing OK 1.10s
82/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_list_error OK 0.65s
83/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_list_empty OK 1.32s
84/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_open_error OK 0.55s
85/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_list_delete OK 2.36s
86/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_list_populated OK 1.26s
87/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_open_error_with_keep_alive OK 0.92s
88/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_quick_enroll OK 0.63s
89/116 libfprint:virtual-driver+virtual-device+VirtualDeviceUnplugging / VirtualDeviceUnplugging.test_device_unplug OK 0.74s
90/116 libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_verify_missing_print OK 0.83s
91/116 libfprint:virtual-driver+virtual-device+VirtualDeviceUnplugging / VirtualDeviceUnplugging.test_device_unplug_during_verify OK 1.22s
92/116 libfprint:drivers / aes3500 OK 2.81s
93/116 libfprint:drivers / elan OK 5.59s
94/116 libfprint:drivers / elan-cobo OK 5.50s
95/116 libfprint:drivers / elanmoc OK 3.59s
96/116 libfprint:drivers / upektc_img OK 3.73s
97/116 libfprint:drivers / synaptics OK 5.11s
98/116 libfprint:drivers / upektc_img-tcs1s OK 3.67s
99/116 libfprint:drivers / uru4000-msv2 OK 3.02s
100/116 libfprint:drivers / uru4000-4500 OK 2.95s
101/116 libfprint:drivers / vfs0050 OK 5.14s
102/116 libfprint:drivers / vfs301 OK 4.91s
103/116 libfprint:drivers / vfs5011 OK 5.98s
104/116 libfprint:drivers / goodixmoc OK 8.99s
105/116 libfprint:drivers / nb1010 OK 3.75s
106/116 libfprint:drivers / egis0570 OK 14.97s
107/116 libfprint:drivers / fpcmoc OK 4.19s
108/116 libfprint:drivers / aes2501 TIMEOUT 75.08s killed by signal 15 SIGTERM
>>> G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=49 G_MESSAGES_DEBUG=all FP_DRIVERS_WHITELIST=aes2501 G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/aes2501
109/116 libfprint:unit-tests / fpi-ssm OK 1.16s
110/116 libfprint:unit-tests / fpi-assembling OK 0.85s
111/116 libfprint:unit-tests / fp-context OK 1.64s
112/116 libfprint:drivers / elanspi TIMEOUT 75.10s killed by signal 15 SIGTERM
>>> MALLOC_PERTURB_=70 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 FP_DRIVERS_WHITELIST=elanspi MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/elanspi
113/116 libfprint / udev-hwdb OK 0.13s
114/116 libfprint:unit-tests / fpi-device OK 24.06s
115/116 libfprint:unit-tests / fp-device OK 4.91s
116/116 libfprint:drivers / vfs7552 TIMEOUT 75.54s killed by signal 15 SIGTERM
>>> G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=74 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests FP_DRIVERS_WHITELIST=vfs7552 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/vfs7552
Ok: 113
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 0
Timeout: 3
Full log written to /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/meson-logs/testlog.txt
cd obj-arm-linux-gnueabihf && tail -v -n \+0 meson-logs/testlog.txt
==> meson-logs/testlog.txt <==
Log of Meson test suite run on 2023-09-16T04:23:37.050551
Inherited environment: SCHROOT_GID=112 DEB_HOST_MULTIARCH=arm-linux-gnueabihf LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_GNU_TYPE=arm-linux-gnueabihf DEB_TARGET_ARCH_LIBC=gnu FFLAGS='-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong' DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_ARCH_BITS=32 DEB_BUILD_OPTIONS=parallel=4 DEB_HOST_ARCH=armhf DEB_TARGET_ARCH_ENDIAN=little SOURCE_DATE_EPOCH=1692861571 OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security' DEB_HOST_ARCH_BITS=32 MAKEFLAGS=w SCHROOT_GROUP=buildd DEB_TARGET_ARCH=armhf DPKG_GENSYMBOLS_CHECK_LEVEL=2 DH_INTERNAL_OPTIONS=-a DEB_HOST_GNU_CPU=arm DEB_BUILD_ARCH_LIBC=gnu MFLAGS=-w DEB_TARGET_ARCH_BITS=32 ASFLAGS='' DEB_BUILD_ARCH_CPU=arm SCHROOT_ALIAS_NAME=trixie-staging-armhf-sbuild DEB_HOST_ARCH_OS=linux SHELL=/bin/sh FCFLAGS='-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong' DEB_HOST_ARCH_CPU=arm SCHROOT_USER=buildd PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games DEB_BUILD_ARCH_ABI=eabihf DEB_BUILD_ARCH=armhf DEB_HOST_ARCH_LIBC=gnu SCHROOT_SESSION_ID=trixie-staging-armhf-sbuild-41cd2286-9212-4cec-8809-e0542a63639b GCJFLAGS='-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong' DEB_TARGET_ARCH_CPU=arm DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_BUILD_ARCH_OS=linux LOGNAME=buildd CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_BUILD_GNU_CPU=arm DEB_TARGET_ARCH_OS=linux USER=buildd DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_MULTIARCH=arm-linux-gnueabihf LDFLAGS=-Wl,-z,relro DEB_TARGET_GNU_TYPE=arm-linux-gnueabihf DEB_TARGET_ARCH_ABI=eabihf CFLAGS='-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security' SCHROOT_UID=107 SCHROOT_COMMAND='dpkg-buildpackage -us -uc -mRaspbian mythic lxc autobuilder 1 <root@raspbian.org> -B -rfakeroot' DFLAGS=-frelease DEB_TARGET_GNU_CPU=arm APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/<<PKGBUILDDIR>>/debian/.debhelper/generated/_source/home DEB_RULES_REQUIRES_ROOT=binary-targets DEB_TARGET_GNU_SYSTEM=linux-gnueabihf DEB_HOST_ARCH_ENDIAN=little OBJCFLAGS='-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security' SCHROOT_CHROOT_NAME=trixie-staging-armhf-sbuild DH_INTERNAL_BUILDFLAGS=1 CXXFLAGS='-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security' DH_INTERNAL_OVERRIDE=dh_auto_test MAKELEVEL=2 XDG_RUNTIME_DIR=/tmp/dh-xdg-rundir-NiQGQtmW MESON_TESTTHREADS=4 DEB_PYTHON_INSTALL_LAYOUT=deb
=================================== 1/116 ====================================
test: libfprint:virtual-driver+virtual-image+VirtualImage / VirtualImage.test_capture_prevents_close
start time: 04:23:37
duration: 1.13s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb MALLOC_PERTURB_=157 G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-image.py VirtualImage.test_capture_prevents_close
----------------------------------- stdout -----------------------------------
(process:17255): libfprint-context-DEBUG: 04:23:37.729: Initializing FpContext (libfprint version 1.94.6)
(process:17255): libfprint-context-DEBUG: 04:23:37.761: No driver found for USB device 1D6B:0003
(process:17255): libfprint-context-DEBUG: 04:23:37.762: No driver found for USB device 0BDA:5401
(process:17255): libfprint-context-DEBUG: 04:23:37.763: No driver found for USB device 1D6B:0002
(process:17255): libfprint-context-DEBUG: 04:23:37.763: No driver found for USB device 1D6B:0003
(process:17255): libfprint-context-DEBUG: 04:23:37.764: No driver found for USB device 0624:0249
(process:17255): libfprint-context-DEBUG: 04:23:37.764: No driver found for USB device 0624:0248
(process:17255): libfprint-context-DEBUG: 04:23:37.765: No driver found for USB device 1D6B:0002
(process:17255): libfprint-context-DEBUG: 04:23:37.765: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-y9rkzf0p/virtual-image.socket
(process:17255): libfprint-context-DEBUG: 04:23:37.767: created
(process:17255): libfprint-device-DEBUG: 04:23:37.782: Device reported probe completion
(process:17255): libfprint-device-DEBUG: 04:23:37.783: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17255): libfprint-device-DEBUG: 04:23:37.784: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:17255): libfprint-virtual_image-DEBUG: 04:23:37.819: 38977917417669: ../libfprint/drivers/virtual-image.c:216
(process:17255): libfprint-virtual_device_connection-DEBUG: 04:23:37.821: 38977917419352: ../libfprint/drivers/virtual-device-listener.c:153
(process:17255): libfprint-image_device-DEBUG: 04:23:37.926: Image device open completed
(process:17255): libfprint-device-DEBUG: 04:23:37.926: Device reported open completion
(process:17255): libfprint-device-DEBUG: 04:23:37.926: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17255): libfprint-device-DEBUG: 04:23:37.927: Updated temperature model after 0.14 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17255): libfprint-device-DEBUG: 04:23:37.934: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17255): libfprint-image_device-DEBUG: 04:23:37.934: Activating image device
(process:17255): libfprint-image_device-DEBUG: 04:23:37.934: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17255): libfprint-image_device-DEBUG: 04:23:37.935: Image device activation completed
(process:17255): libfprint-image_device-DEBUG: 04:23:37.935: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17255): libfprint-image_device-DEBUG: 04:23:37.935: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17255): libfprint-device-DEBUG: 04:23:37.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17255): libfprint-virtual_device_connection-DEBUG: 04:23:37.938: Got a new connection!
(process:17255): libfprint-device-DEBUG: 04:23:37.942: Idle cancelling on ongoing operation!
(process:17255): libfprint-image_device-DEBUG: 04:23:37.950: Deactivating image device
(process:17255): libfprint-image_device-DEBUG: 04:23:37.950: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17255): libfprint-image_device-DEBUG: 04:23:37.950: Image device deactivation completed
(process:17255): libfprint-image_device-DEBUG: 04:23:37.950: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17255): libfprint-device-DEBUG: 04:23:37.951: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE
(process:17255): libfprint-device-DEBUG: 04:23:37.951: Device reported capture completion
(process:17255): libfprint-device-DEBUG: 04:23:37.951: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17255): libfprint-device-DEBUG: 04:23:37.951: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17255): libfprint-device-DEBUG: 04:23:37.952: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17255): libfprint-virtual_image-DEBUG: 04:23:37.958: 38977917555919: ../libfprint/drivers/virtual-image.c:244
(process:17255): libfprint-image_device-DEBUG: 04:23:38.058: Image device close completed
(process:17255): libfprint-device-DEBUG: 04:23:38.059: Device reported close completion
(process:17255): libfprint-device-DEBUG: 04:23:38.059: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17255): libfprint-device-DEBUG: 04:23:38.060: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
Capture operation finished
Capture cancelled as expected
ok
----------------------------------------------------------------------
Ran 1 test in 0.354s
OK
==============================================================================
=================================== 2/116 ====================================
test: libfprint:virtual-driver+virtual-image+VirtualImage / VirtualImage.test_features
start time: 04:23:37
duration: 1.12s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=30 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-image.py VirtualImage.test_features
----------------------------------- stdout -----------------------------------
(process:17259): libfprint-context-DEBUG: 04:23:37.716: Initializing FpContext (libfprint version 1.94.6)
(process:17259): libfprint-context-DEBUG: 04:23:37.771: No driver found for USB device 1D6B:0003
(process:17259): libfprint-context-DEBUG: 04:23:37.771: No driver found for USB device 0BDA:5401
(process:17259): libfprint-context-DEBUG: 04:23:37.771: No driver found for USB device 1D6B:0002
(process:17259): libfprint-context-DEBUG: 04:23:37.771: No driver found for USB device 1D6B:0003
(process:17259): libfprint-context-DEBUG: 04:23:37.771: No driver found for USB device 0624:0249
(process:17259): libfprint-context-DEBUG: 04:23:37.772: No driver found for USB device 0624:0248
(process:17259): libfprint-context-DEBUG: 04:23:37.772: No driver found for USB device 1D6B:0002
(process:17259): libfprint-context-DEBUG: 04:23:37.772: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-mr02ewjc/virtual-image.socket
(process:17259): libfprint-context-DEBUG: 04:23:37.773: created
(process:17259): libfprint-device-DEBUG: 04:23:37.797: Device reported probe completion
(process:17259): libfprint-device-DEBUG: 04:23:37.798: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17259): libfprint-device-DEBUG: 04:23:37.806: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_features (__main__.VirtualImage.test_features) ... (process:17259): libfprint-virtual_image-DEBUG: 04:23:37.862: 38977917460358: ../libfprint/drivers/virtual-image.c:216
(process:17259): libfprint-virtual_device_connection-DEBUG: 04:23:37.864: 38977917462206: ../libfprint/drivers/virtual-device-listener.c:153
(process:17259): libfprint-image_device-DEBUG: 04:23:37.968: Image device open completed
(process:17259): libfprint-device-DEBUG: 04:23:37.968: Device reported open completion
(process:17259): libfprint-device-DEBUG: 04:23:37.969: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17259): libfprint-device-DEBUG: 04:23:37.969: Updated temperature model after 0.16 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17259): libfprint-virtual_image-DEBUG: 04:23:37.972: 38977917570197: ../libfprint/drivers/virtual-image.c:244
(process:17259): libfprint-image_device-DEBUG: 04:23:38.070: Image device close completed
(process:17259): libfprint-device-DEBUG: 04:23:38.071: Device reported close completion
(process:17259): libfprint-device-DEBUG: 04:23:38.071: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17259): libfprint-device-DEBUG: 04:23:38.072: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
----------------------------------------------------------------------
Ran 1 test in 0.387s
OK
==============================================================================
=================================== 3/116 ====================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_capture_unsupported
start time: 04:23:38
duration: 0.80s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=20 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_capture_unsupported
----------------------------------- stdout -----------------------------------
(process:17279): libfprint-context-DEBUG: 04:23:38.781: Initializing FpContext (libfprint version 1.94.6)
(process:17279): libfprint-context-DEBUG: 04:23:38.856: No driver found for USB device 1D6B:0003
(process:17279): libfprint-context-DEBUG: 04:23:38.856: No driver found for USB device 0BDA:5401
(process:17279): libfprint-context-DEBUG: 04:23:38.856: No driver found for USB device 1D6B:0002
(process:17279): libfprint-context-DEBUG: 04:23:38.857: No driver found for USB device 1D6B:0003
(process:17279): libfprint-context-DEBUG: 04:23:38.857: No driver found for USB device 0624:0249
(process:17279): libfprint-context-DEBUG: 04:23:38.857: No driver found for USB device 0624:0248
(process:17279): libfprint-context-DEBUG: 04:23:38.857: No driver found for USB device 1D6B:0002
(process:17279): libfprint-context-DEBUG: 04:23:38.857: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-wcz7m9rp/virtual-device.socket
(process:17279): libfprint-context-DEBUG: 04:23:38.859: created
(process:17279): libfprint-device-DEBUG: 04:23:38.875: Device reported probe completion
(process:17279): libfprint-device-DEBUG: 04:23:38.875: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17279): libfprint-device-DEBUG: 04:23:38.876: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:17279): libfprint-virtual_device-DEBUG: 04:23:38.879: 38977918476748: ../libfprint/drivers/virtual-device.c:387
(process:17279): libfprint-virtual_device_connection-DEBUG: 04:23:38.880: 38977918478090: ../libfprint/drivers/virtual-device-listener.c:153
(process:17279): libfprint-device-DEBUG: 04:23:38.883: Device reported open completion
(process:17279): libfprint-device-DEBUG: 04:23:38.883: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17279): libfprint-device-DEBUG: 04:23:38.883: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17279): libfprint-virtual_device_connection-DEBUG: 04:23:38.905: Got a new connection!
(process:17279): libfprint-virtual_device-DEBUG: 04:23:38.907: Got instructions of length 16
(process:17279): libfprint-virtual_device-DEBUG: 04:23:38.914: Received command SET_KEEP_ALIVE 0
(process:17279): libfprint-virtual_device-DEBUG: 04:23:38.914: Keep alive toggled: 0
(process:17279): libfprint-virtual_device_connection-DEBUG: 04:23:38.917: Got a new connection!
(process:17279): libfprint-virtual_device-DEBUG: 04:23:38.925: Got instructions of length 19
(process:17279): libfprint-virtual_device-DEBUG: 04:23:38.925: Received command SET_ENROLL_STAGES 5
(process:17279): libfprint-device-DEBUG: 04:23:38.927: Device reported close completion
(process:17279): libfprint-device-DEBUG: 04:23:38.928: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17279): libfprint-device-DEBUG: 04:23:38.929: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17279): libfprint-virtual_device-DEBUG: 04:23:38.931: 38977918529085: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.175s
OK
==============================================================================
=================================== 4/116 ====================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_change_enroll_stages
start time: 04:23:39
duration: 0.74s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=111 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_change_enroll_stages
----------------------------------- stdout -----------------------------------
(process:17289): libfprint-context-DEBUG: 04:23:39.569: Initializing FpContext (libfprint version 1.94.6)
(process:17289): libfprint-context-DEBUG: 04:23:39.605: No driver found for USB device 1D6B:0003
(process:17289): libfprint-context-DEBUG: 04:23:39.606: No driver found for USB device 0BDA:5401
(process:17289): libfprint-context-DEBUG: 04:23:39.608: No driver found for USB device 1D6B:0002
(process:17289): libfprint-context-DEBUG: 04:23:39.609: No driver found for USB device 1D6B:0003
(process:17289): libfprint-context-DEBUG: 04:23:39.610: No driver found for USB device 0624:0249
(process:17289): libfprint-context-DEBUG: 04:23:39.610: No driver found for USB device 0624:0248
(process:17289): libfprint-context-DEBUG: 04:23:39.612: No driver found for USB device 1D6B:0002
(process:17289): libfprint-context-DEBUG: 04:23:39.613: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-6ihel9o_/virtual-device.socket
(process:17289): libfprint-context-DEBUG: 04:23:39.615: created
(process:17289): libfprint-device-DEBUG: 04:23:39.626: Device reported probe completion
(process:17289): libfprint-device-DEBUG: 04:23:39.627: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17289): libfprint-device-DEBUG: 04:23:39.627: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:17289): libfprint-virtual_device-DEBUG: 04:23:39.630: 38977919228309: ../libfprint/drivers/virtual-device.c:387
(process:17289): libfprint-virtual_device_connection-DEBUG: 04:23:39.631: 38977919229650: ../libfprint/drivers/virtual-device-listener.c:153
(process:17289): libfprint-device-DEBUG: 04:23:39.635: Device reported open completion
(process:17289): libfprint-device-DEBUG: 04:23:39.635: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17289): libfprint-device-DEBUG: 04:23:39.635: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17289): libfprint-virtual_device_connection-DEBUG: 04:23:39.638: Got a new connection!
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.639: Got instructions of length 20
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.640: Received command SET_ENROLL_STAGES 20
(process:17289): libfprint-virtual_device_connection-DEBUG: 04:23:39.642: Got a new connection!
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.643: Got instructions of length 19
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.643: Received command SET_ENROLL_STAGES 1
(process:17289): libfprint-virtual_device_connection-DEBUG: 04:23:39.647: Got a new connection!
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.648: Got instructions of length 19
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.648: Received command SET_ENROLL_STAGES 0
(process:17289): libfprint-virtual_device_connection-DEBUG: 04:23:39.655: Got a new connection!
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.656: Got instructions of length 16
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.656: Received command SET_KEEP_ALIVE 0
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.656: Keep alive toggled: 0
(process:17289): libfprint-virtual_device_connection-DEBUG: 04:23:39.658: Got a new connection!
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.659: Got instructions of length 19
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.659: Received command SET_ENROLL_STAGES 5
(process:17289): libfprint-device-DEBUG: 04:23:39.661: Device reported close completion
(process:17289): libfprint-device-DEBUG: 04:23:39.661: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17289): libfprint-device-DEBUG: 04:23:39.662: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17289): libfprint-virtual_device-DEBUG: 04:23:39.664: 38977919261773: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.111s
OK
==============================================================================
=================================== 5/116 ====================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_change_scan_type
start time: 04:23:39
duration: 0.95s
result: exit status 0
command: G_DEBUG=fatal-warnings MALLOC_PERTURB_=181 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_change_scan_type
----------------------------------- stdout -----------------------------------
(process:17295): libfprint-context-DEBUG: 04:23:40.448: Initializing FpContext (libfprint version 1.94.6)
(process:17295): libfprint-context-DEBUG: 04:23:40.504: No driver found for USB device 1D6B:0003
(process:17295): libfprint-context-DEBUG: 04:23:40.505: No driver found for USB device 0BDA:5401
(process:17295): libfprint-context-DEBUG: 04:23:40.505: No driver found for USB device 1D6B:0002
(process:17295): libfprint-context-DEBUG: 04:23:40.505: No driver found for USB device 1D6B:0003
(process:17295): libfprint-context-DEBUG: 04:23:40.505: No driver found for USB device 0624:0249
(process:17295): libfprint-context-DEBUG: 04:23:40.505: No driver found for USB device 0624:0248
(process:17295): libfprint-context-DEBUG: 04:23:40.506: No driver found for USB device 1D6B:0002
(process:17295): libfprint-context-DEBUG: 04:23:40.506: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-w40py7sv/virtual-device.socket
(process:17295): libfprint-context-DEBUG: 04:23:40.507: created
(process:17295): libfprint-device-DEBUG: 04:23:40.532: Device reported probe completion
(process:17295): libfprint-device-DEBUG: 04:23:40.533: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17295): libfprint-device-DEBUG: 04:23:40.533: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:17295): libfprint-virtual_device-DEBUG: 04:23:40.537: 38977920135017: ../libfprint/drivers/virtual-device.c:387
(process:17295): libfprint-virtual_device_connection-DEBUG: 04:23:40.547: 38977920145332: ../libfprint/drivers/virtual-device-listener.c:153
(process:17295): libfprint-device-DEBUG: 04:23:40.551: Device reported open completion
(process:17295): libfprint-device-DEBUG: 04:23:40.551: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17295): libfprint-device-DEBUG: 04:23:40.552: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17295): libfprint-virtual_device_connection-DEBUG: 04:23:40.557: Got a new connection!
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.568: Got instructions of length 19
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.569: Received command SET_SCAN_TYPE press
(process:17295): libfprint-virtual_device_connection-DEBUG: 04:23:40.571: Got a new connection!
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.573: Got instructions of length 19
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.573: Received command SET_SCAN_TYPE swipe
(process:17295): libfprint-virtual_device_connection-DEBUG: 04:23:40.577: Got a new connection!
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.587: Got instructions of length 25
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.587: Received command SET_SCAN_TYPE eye-contact
(process:17295): libfprint-virtual_device_connection-DEBUG: 04:23:40.599: Got a new connection!
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.601: Got instructions of length 16
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.601: Received command SET_KEEP_ALIVE 0
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.602: Keep alive toggled: 0
(process:17295): libfprint-virtual_device_connection-DEBUG: 04:23:40.604: Got a new connection!
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.605: Got instructions of length 19
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.606: Received command SET_ENROLL_STAGES 5
(process:17295): libfprint-device-DEBUG: 04:23:40.612: Device reported close completion
(process:17295): libfprint-device-DEBUG: 04:23:40.613: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17295): libfprint-device-DEBUG: 04:23:40.613: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17295): libfprint-virtual_device-DEBUG: 04:23:40.616: 38977920214072: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.192s
OK
==============================================================================
=================================== 6/116 ====================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_close_error
start time: 04:23:40
duration: 0.90s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=79 UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_close_error
----------------------------------- stdout -----------------------------------
(process:17300): libfprint-context-DEBUG: 04:23:41.329: Initializing FpContext (libfprint version 1.94.6)
(process:17300): libfprint-context-DEBUG: 04:23:41.376: No driver found for USB device 1D6B:0003
(process:17300): libfprint-context-DEBUG: 04:23:41.376: No driver found for USB device 0BDA:5401
(process:17300): libfprint-context-DEBUG: 04:23:41.376: No driver found for USB device 1D6B:0002
(process:17300): libfprint-context-DEBUG: 04:23:41.376: No driver found for USB device 1D6B:0003
(process:17300): libfprint-context-DEBUG: 04:23:41.376: No driver found for USB device 0624:0249
(process:17300): libfprint-context-DEBUG: 04:23:41.376: No driver found for USB device 0624:0248
(process:17300): libfprint-context-DEBUG: 04:23:41.377: No driver found for USB device 1D6B:0002
(process:17300): libfprint-context-DEBUG: 04:23:41.377: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-qnx6iys5/virtual-device.socket
(process:17300): libfprint-context-DEBUG: 04:23:41.386: created
(process:17300): libfprint-device-DEBUG: 04:23:41.398: Device reported probe completion
(process:17300): libfprint-device-DEBUG: 04:23:41.398: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17300): libfprint-device-DEBUG: 04:23:41.398: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_close_error (__main__.VirtualDevice.test_close_error) ... (process:17300): libfprint-virtual_device-DEBUG: 04:23:41.401: 38977920999539: ../libfprint/drivers/virtual-device.c:387
(process:17300): libfprint-virtual_device_connection-DEBUG: 04:23:41.407: 38977921005070: ../libfprint/drivers/virtual-device-listener.c:153
(process:17300): libfprint-device-DEBUG: 04:23:41.410: Device reported open completion
(process:17300): libfprint-device-DEBUG: 04:23:41.410: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17300): libfprint-device-DEBUG: 04:23:41.411: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17300): libfprint-virtual_device_connection-DEBUG: 04:23:41.413: Got a new connection!
(process:17300): libfprint-virtual_device-DEBUG: 04:23:41.415: Got instructions of length 9
(process:17300): libfprint-virtual_device-DEBUG: 04:23:41.415: Received command SLEEP 100
(process:17300): libfprint-virtual_device_connection-DEBUG: 04:23:41.422: Got a new connection!
(process:17300): libfprint-virtual_device-DEBUG: 04:23:41.423: Got instructions of length 7
(process:17300): libfprint-virtual_device-DEBUG: 04:23:41.423: Received command ERROR 4
(process:17300): libfprint-virtual_device-DEBUG: 04:23:41.426: Processing command SLEEP 100
(process:17300): libfprint-virtual_device-DEBUG: 04:23:41.426: Sleeping 100ms
(process:17300): libfprint-virtual_device-DEBUG: 04:23:41.530: Sleeping completed
(process:17300): libfprint-virtual_device-DEBUG: 04:23:41.530: Processing command ERROR 4
(process:17300): libfprint-device-DEBUG: 04:23:41.530: Device reported close completion
(process:17300): libfprint-device-DEBUG: 04:23:41.531: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17300): libfprint-device-DEBUG: 04:23:41.531: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
----------------------------------------------------------------------
Ran 1 test in 0.234s
OK
(process:17300): libfprint-virtual_device-DEBUG: 04:23:41.560: 38977921158578: ../libfprint/drivers/virtual-device.c:752
==============================================================================
=================================== 7/116 ====================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_close_while_opening
start time: 04:23:41
duration: 1.24s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MALLOC_PERTURB_=248 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_close_while_opening
----------------------------------- stdout -----------------------------------
(process:17305): libfprint-context-DEBUG: 04:23:42.161: Initializing FpContext (libfprint version 1.94.6)
(process:17305): libfprint-context-DEBUG: 04:23:42.193: No driver found for USB device 1D6B:0003
(process:17305): libfprint-context-DEBUG: 04:23:42.193: No driver found for USB device 0BDA:5401
(process:17305): libfprint-context-DEBUG: 04:23:42.194: No driver found for USB device 1D6B:0002
(process:17305): libfprint-context-DEBUG: 04:23:42.194: No driver found for USB device 1D6B:0003
(process:17305): libfprint-context-DEBUG: 04:23:42.194: No driver found for USB device 0624:0249
(process:17305): libfprint-context-DEBUG: 04:23:42.194: No driver found for USB device 0624:0248
(process:17305): libfprint-context-DEBUG: 04:23:42.194: No driver found for USB device 1D6B:0002
(process:17305): libfprint-context-DEBUG: 04:23:42.194: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-s23kz2vt/virtual-device.socket
(process:17305): libfprint-context-DEBUG: 04:23:42.196: created
(process:17305): libfprint-device-DEBUG: 04:23:42.208: Device reported probe completion
(process:17305): libfprint-device-DEBUG: 04:23:42.209: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17305): libfprint-device-DEBUG: 04:23:42.210: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:17305): libfprint-virtual_device-DEBUG: 04:23:42.214: 38977921812187: ../libfprint/drivers/virtual-device.c:387
(process:17305): libfprint-virtual_device_connection-DEBUG: 04:23:42.216: 38977921813844: ../libfprint/drivers/virtual-device-listener.c:153
(process:17305): libfprint-device-DEBUG: 04:23:42.219: Device reported open completion
(process:17305): libfprint-device-DEBUG: 04:23:42.220: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17305): libfprint-device-DEBUG: 04:23:42.220: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17305): libfprint-virtual_device_connection-DEBUG: 04:23:42.223: Got a new connection!
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.225: Got instructions of length 16
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.226: Received command SET_KEEP_ALIVE 1
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.226: Keep alive toggled: 1
(process:17305): libfprint-device-DEBUG: 04:23:42.228: Device reported close completion
(process:17305): libfprint-device-DEBUG: 04:23:42.228: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17305): libfprint-device-DEBUG: 04:23:42.229: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17305): libfprint-virtual_device_connection-DEBUG: 04:23:42.231: Got a new connection!
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.232: Got instructions of length 9
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.233: Received command SLEEP 500
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.236: 38977921834030: ../libfprint/drivers/virtual-device.c:387
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.236: Processing command SLEEP 500
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.237: Sleeping 500ms
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.742: Sleeping completed
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.743: 38977922340755: ../libfprint/drivers/virtual-device.c:387
(process:17305): libfprint-device-DEBUG: 04:23:42.743: Device reported open completion
(process:17305): libfprint-device-DEBUG: 04:23:42.744: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17305): libfprint-device-DEBUG: 04:23:42.744: Updated temperature model after 0.52 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17305): libfprint-virtual_device_connection-DEBUG: 04:23:42.747: Got a new connection!
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.749: Got instructions of length 16
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.749: Received command SET_KEEP_ALIVE 0
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.750: Keep alive toggled: 0
(process:17305): libfprint-virtual_device_connection-DEBUG: 04:23:42.752: Got a new connection!
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.753: Got instructions of length 19
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.753: Received command SET_ENROLL_STAGES 5
(process:17305): libfprint-device-DEBUG: 04:23:42.759: Device reported close completion
(process:17305): libfprint-device-DEBUG: 04:23:42.760: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17305): libfprint-device-DEBUG: 04:23:42.760: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17305): libfprint-virtual_device-DEBUG: 04:23:42.762: 38977922360701: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.622s
OK
==============================================================================
=================================== 8/116 ====================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_delayed_open
start time: 04:23:42
duration: 1.13s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=239 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_delayed_open
----------------------------------- stdout -----------------------------------
(process:17310): libfprint-context-DEBUG: 04:23:43.280: Initializing FpContext (libfprint version 1.94.6)
(process:17310): libfprint-context-DEBUG: 04:23:43.315: No driver found for USB device 1D6B:0003
(process:17310): libfprint-context-DEBUG: 04:23:43.315: No driver found for USB device 0BDA:5401
(process:17310): libfprint-context-DEBUG: 04:23:43.316: No driver found for USB device 1D6B:0002
(process:17310): libfprint-context-DEBUG: 04:23:43.316: No driver found for USB device 1D6B:0003
(process:17310): libfprint-context-DEBUG: 04:23:43.317: No driver found for USB device 0624:0249
(process:17310): libfprint-context-DEBUG: 04:23:43.317: No driver found for USB device 0624:0248
(process:17310): libfprint-context-DEBUG: 04:23:43.317: No driver found for USB device 1D6B:0002
(process:17310): libfprint-context-DEBUG: 04:23:43.318: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-9bnw4h6j/virtual-device.socket
(process:17310): libfprint-context-DEBUG: 04:23:43.319: created
(process:17310): libfprint-device-DEBUG: 04:23:43.333: Device reported probe completion
(process:17310): libfprint-device-DEBUG: 04:23:43.334: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17310): libfprint-device-DEBUG: 04:23:43.335: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:17310): libfprint-virtual_device-DEBUG: 04:23:43.338: 38977922936595: ../libfprint/drivers/virtual-device.c:387
(process:17310): libfprint-virtual_device_connection-DEBUG: 04:23:43.340: 38977922938242: ../libfprint/drivers/virtual-device-listener.c:153
(process:17310): libfprint-device-DEBUG: 04:23:43.343: Device reported open completion
(process:17310): libfprint-device-DEBUG: 04:23:43.344: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17310): libfprint-device-DEBUG: 04:23:43.345: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17310): libfprint-virtual_device_connection-DEBUG: 04:23:43.348: Got a new connection!
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.350: Got instructions of length 16
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.350: Received command IGNORED_COMMAND
(process:17310): libfprint-virtual_device_connection-DEBUG: 04:23:43.352: Got a new connection!
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.354: Got instructions of length 9
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.354: Received command SLEEP 500
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.357: Processing command IGNORED_COMMAND
(process:17310): libfprint-device-DEBUG: 04:23:43.358: Device reported close completion
(process:17310): libfprint-device-DEBUG: 04:23:43.358: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17310): libfprint-device-DEBUG: 04:23:43.359: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.366: 38977922964371: ../libfprint/drivers/virtual-device.c:387
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.367: Processing command SLEEP 500
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.367: Sleeping 500ms
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.869: Sleeping completed
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.869: 38977923467372: ../libfprint/drivers/virtual-device.c:387
(process:17310): libfprint-virtual_device_connection-DEBUG: 04:23:43.869: 38977923467646: ../libfprint/drivers/virtual-device-listener.c:153
(process:17310): libfprint-device-DEBUG: 04:23:43.871: Device reported open completion
(process:17310): libfprint-device-DEBUG: 04:23:43.871: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17310): libfprint-device-DEBUG: 04:23:43.871: Updated temperature model after 0.51 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17310): libfprint-virtual_device_connection-DEBUG: 04:23:43.875: Got a new connection!
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.877: Got instructions of length 16
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.877: Received command SET_KEEP_ALIVE 0
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.878: Keep alive toggled: 0
(process:17310): libfprint-virtual_device_connection-DEBUG: 04:23:43.880: Got a new connection!
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.881: Got instructions of length 19
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.881: Received command SET_ENROLL_STAGES 5
(process:17310): libfprint-device-DEBUG: 04:23:43.883: Device reported close completion
(process:17310): libfprint-device-DEBUG: 04:23:43.884: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17310): libfprint-device-DEBUG: 04:23:43.884: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17310): libfprint-virtual_device-DEBUG: 04:23:43.898: 38977923496294: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.629s
OK
==============================================================================
=================================== 9/116 ====================================
test: libfprint:virtual-driver+virtual-image+VirtualImage / VirtualImage.test_verify_serialized
start time: 04:23:38
duration: 6.52s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 MALLOC_PERTURB_=153 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-image.py VirtualImage.test_verify_serialized
----------------------------------- stdout -----------------------------------
(process:17277): libfprint-context-DEBUG: 04:23:38.838: Initializing FpContext (libfprint version 1.94.6)
(process:17277): libfprint-context-DEBUG: 04:23:38.912: No driver found for USB device 1D6B:0003
(process:17277): libfprint-context-DEBUG: 04:23:38.912: No driver found for USB device 0BDA:5401
(process:17277): libfprint-context-DEBUG: 04:23:38.913: No driver found for USB device 1D6B:0002
(process:17277): libfprint-context-DEBUG: 04:23:38.913: No driver found for USB device 1D6B:0003
(process:17277): libfprint-context-DEBUG: 04:23:38.913: No driver found for USB device 0624:0249
(process:17277): libfprint-context-DEBUG: 04:23:38.913: No driver found for USB device 0624:0248
(process:17277): libfprint-context-DEBUG: 04:23:38.913: No driver found for USB device 1D6B:0002
(process:17277): libfprint-context-DEBUG: 04:23:38.913: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ag2dfahw/virtual-image.socket
(process:17277): libfprint-context-DEBUG: 04:23:38.923: created
(process:17277): libfprint-device-DEBUG: 04:23:38.945: Device reported probe completion
(process:17277): libfprint-device-DEBUG: 04:23:38.945: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17277): libfprint-device-DEBUG: 04:23:38.946: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:17277): libfprint-virtual_image-DEBUG: 04:23:39.009: 38977918607138: ../libfprint/drivers/virtual-image.c:216
(process:17277): libfprint-virtual_device_connection-DEBUG: 04:23:39.015: 38977918613366: ../libfprint/drivers/virtual-device-listener.c:153
(process:17277): libfprint-image_device-DEBUG: 04:23:39.126: Image device open completed
(process:17277): libfprint-device-DEBUG: 04:23:39.126: Device reported open completion
(process:17277): libfprint-device-DEBUG: 04:23:39.126: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17277): libfprint-device-DEBUG: 04:23:39.127: Updated temperature model after 0.18 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17277): libfprint-device-DEBUG: 04:23:39.151: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17277): libfprint-image_device-DEBUG: 04:23:39.151: Activating image device
(process:17277): libfprint-image_device-DEBUG: 04:23:39.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17277): libfprint-image_device-DEBUG: 04:23:39.152: Image device activation completed
(process:17277): libfprint-image_device-DEBUG: 04:23:39.152: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.152: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17277): libfprint-device-DEBUG: 04:23:39.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17277): libfprint-virtual_device_connection-DEBUG: 04:23:39.155: Got a new connection!
(process:17277): libfprint-virtual_image-DEBUG: 04:23:39.157: image data: 0xb3c110
(process:17277): libfprint-device-DEBUG: 04:23:39.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-image_device-DEBUG: 04:23:39.167: Image device reported finger status: on
(process:17277): libfprint-image_device-DEBUG: 04:23:39.167: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.167: Image device captured an image
(process:17277): libfprint-image_device-DEBUG: 04:23:39.168: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17277): libfprint-device-DEBUG: 04:23:39.168: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-device-DEBUG: 04:23:39.168: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.168: Image device reported finger status: off
(process:17277): libfprint-image_device-DEBUG: 04:23:39.168: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17277): libfprint-device-DEBUG: 04:23:39.256: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17277): libfprint-image-DEBUG: 04:23:39.334: Minutiae scan completed in 0.163880 secs
(process:17277): libfprint-device-DEBUG: 04:23:39.338: Device reported enroll progress, reported 1 of 5 have been completed
(process:17277): libfprint-image_device-DEBUG: 04:23:39.339: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17277): libfprint-device-DEBUG: 04:23:39.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17277): libfprint-device-DEBUG: 04:23:39.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-image_device-DEBUG: 04:23:39.343: Image device reported finger status: on
(process:17277): libfprint-image_device-DEBUG: 04:23:39.343: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17277): libfprint-virtual_image-DEBUG: 04:23:39.345: image data: 0xb3c110
(process:17277): libfprint-image_device-DEBUG: 04:23:39.351: Image device captured an image
(process:17277): libfprint-image_device-DEBUG: 04:23:39.351: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17277): libfprint-device-DEBUG: 04:23:39.351: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-image-DEBUG: 04:23:39.513: Minutiae scan completed in 0.160922 secs
(process:17277): libfprint-device-DEBUG: 04:23:39.514: Device reported enroll progress, reported 2 of 5 have been completed
(process:17277): libfprint-device-DEBUG: 04:23:39.516: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.516: Image device reported finger status: off
(process:17277): libfprint-image_device-DEBUG: 04:23:39.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17277): libfprint-device-DEBUG: 04:23:39.516: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17277): libfprint-virtual_image-DEBUG: 04:23:39.524: image data: 0xb3c110
(process:17277): libfprint-device-DEBUG: 04:23:39.525: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-image_device-DEBUG: 04:23:39.525: Image device reported finger status: on
(process:17277): libfprint-image_device-DEBUG: 04:23:39.525: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.526: Image device captured an image
(process:17277): libfprint-image_device-DEBUG: 04:23:39.530: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17277): libfprint-device-DEBUG: 04:23:39.530: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-device-DEBUG: 04:23:39.530: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.530: Image device reported finger status: off
(process:17277): libfprint-image_device-DEBUG: 04:23:39.531: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17277): libfprint-image-DEBUG: 04:23:39.696: Minutiae scan completed in 0.164583 secs
(process:17277): libfprint-device-DEBUG: 04:23:39.696: Device reported enroll progress, reported 3 of 5 have been completed
(process:17277): libfprint-image_device-DEBUG: 04:23:39.697: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17277): libfprint-device-DEBUG: 04:23:39.697: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17277): libfprint-virtual_image-DEBUG: 04:23:39.699: image data: 0xb3c110
(process:17277): libfprint-device-DEBUG: 04:23:39.700: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-image_device-DEBUG: 04:23:39.701: Image device reported finger status: on
(process:17277): libfprint-image_device-DEBUG: 04:23:39.701: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.701: Image device captured an image
(process:17277): libfprint-image_device-DEBUG: 04:23:39.701: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17277): libfprint-device-DEBUG: 04:23:39.701: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-device-DEBUG: 04:23:39.701: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.702: Image device reported finger status: off
(process:17277): libfprint-image_device-DEBUG: 04:23:39.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17277): libfprint-image-DEBUG: 04:23:39.857: Minutiae scan completed in 0.154660 secs
(process:17277): libfprint-device-DEBUG: 04:23:39.857: Device reported enroll progress, reported 4 of 5 have been completed
(process:17277): libfprint-image_device-DEBUG: 04:23:39.858: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17277): libfprint-device-DEBUG: 04:23:39.858: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17277): libfprint-virtual_image-DEBUG: 04:23:39.860: image data: 0xb3c110
(process:17277): libfprint-device-DEBUG: 04:23:39.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-image_device-DEBUG: 04:23:39.861: Image device reported finger status: on
(process:17277): libfprint-image_device-DEBUG: 04:23:39.861: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.862: Image device captured an image
(process:17277): libfprint-image_device-DEBUG: 04:23:39.862: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17277): libfprint-device-DEBUG: 04:23:39.862: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-device-DEBUG: 04:23:39.862: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17277): libfprint-image_device-DEBUG: 04:23:39.862: Image device reported finger status: off
(process:17277): libfprint-image_device-DEBUG: 04:23:39.863: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17277): libfprint-image-DEBUG: 04:23:40.005: Minutiae scan completed in 0.141913 secs
(process:17277): libfprint-device-DEBUG: 04:23:40.006: Device reported enroll progress, reported 5 of 5 have been completed
(process:17277): libfprint-image_device-DEBUG: 04:23:40.007: Deactivating image device
(process:17277): libfprint-image_device-DEBUG: 04:23:40.007: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17277): libfprint-image_device-DEBUG: 04:23:40.007: Image device deactivation completed
(process:17277): libfprint-image_device-DEBUG: 04:23:40.007: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17277): libfprint-device-DEBUG: 04:23:40.007: Device reported enroll completion
(process:17277): libfprint-device-DEBUG: 04:23:40.008: Print for finger FP_FINGER_LEFT_THUMB enrolled
(process:17277): libfprint-device-DEBUG: 04:23:40.008: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17277): libfprint-device-DEBUG: 04:23:40.008: Updated temperature model after 0.75 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17277): libfprint-device-DEBUG: 04:23:40.042: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17277): libfprint-image_device-DEBUG: 04:23:40.043: Activating image device
(process:17277): libfprint-image_device-DEBUG: 04:23:40.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17277): libfprint-image_device-DEBUG: 04:23:40.043: Image device activation completed
(process:17277): libfprint-image_device-DEBUG: 04:23:40.044: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17277): libfprint-image_device-DEBUG: 04:23:40.044: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17277): libfprint-device-DEBUG: 04:23:40.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17277): libfprint-virtual_image-DEBUG: 04:23:40.045: image data: 0xb43298
(process:17277): libfprint-device-DEBUG: 04:23:40.047: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-image_device-DEBUG: 04:23:40.047: Image device reported finger status: on
(process:17277): libfprint-image_device-DEBUG: 04:23:40.048: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17277): libfprint-image_device-DEBUG: 04:23:40.048: Image device captured an image
(process:17277): libfprint-image_device-DEBUG: 04:23:40.048: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17277): libfprint-device-DEBUG: 04:23:40.048: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-device-DEBUG: 04:23:40.048: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17277): libfprint-image_device-DEBUG: 04:23:40.049: Image device reported finger status: off
(process:17277): libfprint-image_device-DEBUG: 04:23:40.049: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17277): libfprint-image_device-DEBUG: 04:23:40.049: Deactivating image device
(process:17277): libfprint-image_device-DEBUG: 04:23:40.049: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17277): libfprint-image_device-DEBUG: 04:23:40.049: Image device deactivation completed
(process:17277): libfprint-image_device-DEBUG: 04:23:40.049: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17277): libfprint-image-DEBUG: 04:23:40.198: Minutiae scan completed in 0.147932 secs
(process:17277): libfprint-print-DEBUG: 04:23:44.163: score 1093/40
(process:17277): libfprint-device-DEBUG: 04:23:44.164: Device reported verify result
(process:17277): libfprint-device-DEBUG: 04:23:44.164: Device reported verify completion
(process:17277): libfprint-device-DEBUG: 04:23:44.165: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17277): libfprint-device-DEBUG: 04:23:44.166: Updated temperature model after 4.12 seconds, ratio 0.27 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17277): libfprint-device-DEBUG: 04:23:44.169: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17277): libfprint-image_device-DEBUG: 04:23:44.169: Activating image device
(process:17277): libfprint-image_device-DEBUG: 04:23:44.170: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17277): libfprint-image_device-DEBUG: 04:23:44.171: Image device activation completed
(process:17277): libfprint-image_device-DEBUG: 04:23:44.171: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17277): libfprint-image_device-DEBUG: 04:23:44.171: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17277): libfprint-device-DEBUG: 04:23:44.172: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17277): libfprint-virtual_image-DEBUG: 04:23:44.173: image data: 0xb45438
(process:17277): libfprint-device-DEBUG: 04:23:44.176: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-image_device-DEBUG: 04:23:44.176: Image device reported finger status: on
(process:17277): libfprint-image_device-DEBUG: 04:23:44.177: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17277): libfprint-image_device-DEBUG: 04:23:44.177: Image device captured an image
(process:17277): libfprint-image_device-DEBUG: 04:23:44.194: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17277): libfprint-device-DEBUG: 04:23:44.194: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17277): libfprint-device-DEBUG: 04:23:44.195: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17277): libfprint-image_device-DEBUG: 04:23:44.195: Image device reported finger status: off
(process:17277): libfprint-image_device-DEBUG: 04:23:44.196: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17277): libfprint-image_device-DEBUG: 04:23:44.196: Deactivating image device
(process:17277): libfprint-image_device-DEBUG: 04:23:44.196: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17277): libfprint-image_device-DEBUG: 04:23:44.197: Image device deactivation completed
(process:17277): libfprint-image_device-DEBUG: 04:23:44.197: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17277): libfprint-image-DEBUG: 04:23:44.313: Minutiae scan completed in 0.134847 secs
(process:17277): libfprint-print-DEBUG: 04:23:44.337: score 10/40
(process:17277): libfprint-print-DEBUG: 04:23:44.387: score 10/40
(process:17277): libfprint-print-DEBUG: 04:23:44.423: score 10/40
(process:17277): libfprint-print-DEBUG: 04:23:44.448: score 10/40
(process:17277): libfprint-print-DEBUG: 04:23:44.470: score 10/40
(process:17277): libfprint-device-DEBUG: 04:23:44.471: Device reported verify result
(process:17277): libfprint-device-DEBUG: 04:23:44.471: Device reported verify completion
(process:17277): libfprint-device-DEBUG: 04:23:44.472: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17277): libfprint-device-DEBUG: 04:23:44.473: Updated temperature model after 0.30 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17277): libfprint-virtual_image-DEBUG: 04:23:44.474: 38977924072729: ../libfprint/drivers/virtual-image.c:244
(process:17277): libfprint-image_device-DEBUG: 04:23:44.575: Image device close completed
(process:17277): libfprint-device-DEBUG: 04:23:44.575: Device reported close completion
(process:17277): libfprint-device-DEBUG: 04:23:44.575: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17277): libfprint-device-DEBUG: 04:23:44.576: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Enroll done
ok
----------------------------------------------------------------------
Ran 1 test in 5.766s
OK
==============================================================================
=================================== 10/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_delayed_open_with_keep_alive
start time: 04:23:44
duration: 1.31s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=241 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_delayed_open_with_keep_alive
----------------------------------- stdout -----------------------------------
(process:17315): libfprint-context-DEBUG: 04:23:44.629: Initializing FpContext (libfprint version 1.94.6)
(process:17315): libfprint-context-DEBUG: 04:23:44.679: No driver found for USB device 1D6B:0003
(process:17315): libfprint-context-DEBUG: 04:23:44.680: No driver found for USB device 0BDA:5401
(process:17315): libfprint-context-DEBUG: 04:23:44.680: No driver found for USB device 1D6B:0002
(process:17315): libfprint-context-DEBUG: 04:23:44.680: No driver found for USB device 1D6B:0003
(process:17315): libfprint-context-DEBUG: 04:23:44.680: No driver found for USB device 0624:0249
(process:17315): libfprint-context-DEBUG: 04:23:44.680: No driver found for USB device 0624:0248
(process:17315): libfprint-context-DEBUG: 04:23:44.680: No driver found for USB device 1D6B:0002
(process:17315): libfprint-context-DEBUG: 04:23:44.681: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-4rpvbpc6/virtual-device.socket
(process:17315): libfprint-context-DEBUG: 04:23:44.690: created
(process:17315): libfprint-device-DEBUG: 04:23:44.700: Device reported probe completion
(process:17315): libfprint-device-DEBUG: 04:23:44.701: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17315): libfprint-device-DEBUG: 04:23:44.701: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:17315): libfprint-virtual_device-DEBUG: 04:23:44.708: 38977924306349: ../libfprint/drivers/virtual-device.c:387
(process:17315): libfprint-virtual_device_connection-DEBUG: 04:23:44.709: 38977924307656: ../libfprint/drivers/virtual-device-listener.c:153
(process:17315): libfprint-device-DEBUG: 04:23:44.712: Device reported open completion
(process:17315): libfprint-device-DEBUG: 04:23:44.713: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17315): libfprint-device-DEBUG: 04:23:44.713: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17315): libfprint-virtual_device_connection-DEBUG: 04:23:44.716: Got a new connection!
(process:17315): libfprint-virtual_device-DEBUG: 04:23:44.717: Got instructions of length 16
(process:17315): libfprint-virtual_device-DEBUG: 04:23:44.717: Received command SET_KEEP_ALIVE 1
(process:17315): libfprint-virtual_device-DEBUG: 04:23:44.717: Keep alive toggled: 1
(process:17315): libfprint-device-DEBUG: 04:23:44.719: Device reported close completion
(process:17315): libfprint-device-DEBUG: 04:23:44.719: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17315): libfprint-device-DEBUG: 04:23:44.719: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17315): libfprint-virtual_device_connection-DEBUG: 04:23:44.720: Got a new connection!
(process:17315): libfprint-virtual_device-DEBUG: 04:23:44.721: Got instructions of length 9
(process:17315): libfprint-virtual_device-DEBUG: 04:23:44.722: Received command SLEEP 500
(process:17315): libfprint-virtual_device-DEBUG: 04:23:44.732: 38977924330707: ../libfprint/drivers/virtual-device.c:387
(process:17315): libfprint-virtual_device-DEBUG: 04:23:44.733: Processing command SLEEP 500
(process:17315): libfprint-virtual_device-DEBUG: 04:23:44.733: Sleeping 500ms
(process:17315): libfprint-virtual_device-DEBUG: 04:23:45.234: Sleeping completed
(process:17315): libfprint-virtual_device-DEBUG: 04:23:45.234: 38977924832277: ../libfprint/drivers/virtual-device.c:387
(process:17315): libfprint-device-DEBUG: 04:23:45.234: Device reported open completion
(process:17315): libfprint-device-DEBUG: 04:23:45.234: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17315): libfprint-device-DEBUG: 04:23:45.235: Updated temperature model after 0.52 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17315): libfprint-virtual_device_connection-DEBUG: 04:23:45.238: Got a new connection!
(process:17315): libfprint-virtual_device-DEBUG: 04:23:45.239: Got instructions of length 16
(process:17315): libfprint-virtual_device-DEBUG: 04:23:45.239: Received command SET_KEEP_ALIVE 0
(process:17315): libfprint-virtual_device-DEBUG: 04:23:45.239: Keep alive toggled: 0
(process:17315): libfprint-virtual_device_connection-DEBUG: 04:23:45.241: Got a new connection!
(process:17315): libfprint-virtual_device-DEBUG: 04:23:45.242: Got instructions of length 19
(process:17315): libfprint-virtual_device-DEBUG: 04:23:45.242: Received command SET_ENROLL_STAGES 5
(process:17315): libfprint-device-DEBUG: 04:23:45.247: Device reported close completion
(process:17315): libfprint-device-DEBUG: 04:23:45.247: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17315): libfprint-device-DEBUG: 04:23:45.248: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17315): libfprint-virtual_device-DEBUG: 04:23:45.255: 38977924852838: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.643s
OK
==============================================================================
=================================== 11/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_device_features
start time: 04:23:44
duration: 0.87s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=137 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_device_features
----------------------------------- stdout -----------------------------------
(process:17321): libfprint-context-DEBUG: 04:23:45.348: Initializing FpContext (libfprint version 1.94.6)
(process:17321): libfprint-context-DEBUG: 04:23:45.403: No driver found for USB device 1D6B:0003
(process:17321): libfprint-context-DEBUG: 04:23:45.404: No driver found for USB device 0BDA:5401
(process:17321): libfprint-context-DEBUG: 04:23:45.404: No driver found for USB device 1D6B:0002
(process:17321): libfprint-context-DEBUG: 04:23:45.404: No driver found for USB device 1D6B:0003
(process:17321): libfprint-context-DEBUG: 04:23:45.405: No driver found for USB device 0624:0249
(process:17321): libfprint-context-DEBUG: 04:23:45.405: No driver found for USB device 0624:0248
(process:17321): libfprint-context-DEBUG: 04:23:45.406: No driver found for USB device 1D6B:0002
(process:17321): libfprint-context-DEBUG: 04:23:45.406: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-pwx0ot6c/virtual-device.socket
(process:17321): libfprint-context-DEBUG: 04:23:45.408: created
(process:17321): libfprint-device-DEBUG: 04:23:45.432: Device reported probe completion
(process:17321): libfprint-device-DEBUG: 04:23:45.433: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17321): libfprint-device-DEBUG: 04:23:45.434: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_device_features (__main__.VirtualDevice.test_device_features) ... (process:17321): libfprint-virtual_device-DEBUG: 04:23:45.437: 38977925035601: ../libfprint/drivers/virtual-device.c:387
(process:17321): libfprint-virtual_device_connection-DEBUG: 04:23:45.443: 38977925041423: ../libfprint/drivers/virtual-device-listener.c:153
(process:17321): libfprint-device-DEBUG: 04:23:45.451: Device reported open completion
(process:17321): libfprint-device-DEBUG: 04:23:45.451: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17321): libfprint-device-DEBUG: 04:23:45.452: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17321): libfprint-virtual_device_connection-DEBUG: 04:23:45.456: Got a new connection!
(process:17321): libfprint-virtual_device-DEBUG: 04:23:45.467: Got instructions of length 16
(process:17321): libfprint-virtual_device-DEBUG: 04:23:45.467: Received command SET_KEEP_ALIVE 0
(process:17321): libfprint-virtual_device-DEBUG: 04:23:45.468: Keep alive toggled: 0
(process:17321): libfprint-virtual_device_connection-DEBUG: 04:23:45.470: Got a new connection!
(process:17321): libfprint-virtual_device-DEBUG: 04:23:45.471: Got instructions of length 19
(process:17321): libfprint-virtual_device-DEBUG: 04:23:45.471: Received command SET_ENROLL_STAGES 5
(process:17321): libfprint-device-DEBUG: 04:23:45.473: Device reported close completion
(process:17321): libfprint-device-DEBUG: 04:23:45.474: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17321): libfprint-device-DEBUG: 04:23:45.475: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17321): libfprint-virtual_device-DEBUG: 04:23:45.477: 38977925075128: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.151s
OK
==============================================================================
=================================== 12/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_device_properties
start time: 04:23:45
duration: 0.70s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=188 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_device_properties
----------------------------------- stdout -----------------------------------
(process:17323): libfprint-context-DEBUG: 04:23:45.786: Initializing FpContext (libfprint version 1.94.6)
(process:17323): libfprint-context-DEBUG: 04:23:45.850: No driver found for USB device 1D6B:0003
(process:17323): libfprint-context-DEBUG: 04:23:45.850: No driver found for USB device 0BDA:5401
(process:17323): libfprint-context-DEBUG: 04:23:45.851: No driver found for USB device 1D6B:0002
(process:17323): libfprint-context-DEBUG: 04:23:45.851: No driver found for USB device 1D6B:0003
(process:17323): libfprint-context-DEBUG: 04:23:45.851: No driver found for USB device 0624:0249
(process:17323): libfprint-context-DEBUG: 04:23:45.851: No driver found for USB device 0624:0248
(process:17323): libfprint-context-DEBUG: 04:23:45.851: No driver found for USB device 1D6B:0002
(process:17323): libfprint-context-DEBUG: 04:23:45.851: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-30106cik/virtual-device.socket
(process:17323): libfprint-context-DEBUG: 04:23:45.853: created
(process:17323): libfprint-device-DEBUG: 04:23:45.864: Device reported probe completion
(process:17323): libfprint-device-DEBUG: 04:23:45.878: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17323): libfprint-device-DEBUG: 04:23:45.879: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:17323): libfprint-virtual_device-DEBUG: 04:23:45.882: 38977925480581: ../libfprint/drivers/virtual-device.c:387
(process:17323): libfprint-virtual_device_connection-DEBUG: 04:23:45.884: 38977925482161: ../libfprint/drivers/virtual-device-listener.c:153
(process:17323): libfprint-device-DEBUG: 04:23:45.887: Device reported open completion
(process:17323): libfprint-device-DEBUG: 04:23:45.888: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17323): libfprint-device-DEBUG: 04:23:45.888: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17323): libfprint-virtual_device_connection-DEBUG: 04:23:45.902: Got a new connection!
(process:17323): libfprint-virtual_device-DEBUG: 04:23:45.904: Got instructions of length 16
(process:17323): libfprint-virtual_device-DEBUG: 04:23:45.918: Received command SET_KEEP_ALIVE 0
(process:17323): libfprint-virtual_device-DEBUG: 04:23:45.918: Keep alive toggled: 0
(process:17323): libfprint-virtual_device_connection-DEBUG: 04:23:45.921: Got a new connection!
(process:17323): libfprint-virtual_device-DEBUG: 04:23:45.922: Got instructions of length 19
(process:17323): libfprint-virtual_device-DEBUG: 04:23:45.922: Received command SET_ENROLL_STAGES 5
(process:17323): libfprint-device-DEBUG: 04:23:45.924: Device reported close completion
(process:17323): libfprint-device-DEBUG: 04:23:45.925: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17323): libfprint-device-DEBUG: 04:23:45.925: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17323): libfprint-virtual_device-DEBUG: 04:23:45.928: 38977925525909: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.173s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated
self.assertFalse(self.dev.supports_identify())
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated
self.assertFalse(self.dev.supports_capture())
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated
self.assertFalse(self.dev.has_storage())
==============================================================================
=================================== 13/116 ===================================
test: libfprint:virtual-driver+virtual-image+VirtualImage / VirtualImage.test_identify
start time: 04:23:37
duration: 9.42s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=80 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-image.py VirtualImage.test_identify
----------------------------------- stdout -----------------------------------
(process:17261): libfprint-context-DEBUG: 04:23:37.733: Initializing FpContext (libfprint version 1.94.6)
(process:17261): libfprint-context-DEBUG: 04:23:37.795: No driver found for USB device 1D6B:0003
(process:17261): libfprint-context-DEBUG: 04:23:37.795: No driver found for USB device 0BDA:5401
(process:17261): libfprint-context-DEBUG: 04:23:37.795: No driver found for USB device 1D6B:0002
(process:17261): libfprint-context-DEBUG: 04:23:37.795: No driver found for USB device 1D6B:0003
(process:17261): libfprint-context-DEBUG: 04:23:37.796: No driver found for USB device 0624:0249
(process:17261): libfprint-context-DEBUG: 04:23:37.796: No driver found for USB device 0624:0248
(process:17261): libfprint-context-DEBUG: 04:23:37.796: No driver found for USB device 1D6B:0002
(process:17261): libfprint-context-DEBUG: 04:23:37.796: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-_piqfkw8/virtual-image.socket
(process:17261): libfprint-context-DEBUG: 04:23:37.798: created
(process:17261): libfprint-device-DEBUG: 04:23:37.810: Device reported probe completion
(process:17261): libfprint-device-DEBUG: 04:23:37.818: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17261): libfprint-device-DEBUG: 04:23:37.818: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_identify (__main__.VirtualImage.test_identify) ... (process:17261): libfprint-virtual_image-DEBUG: 04:23:37.878: 38977917476698: ../libfprint/drivers/virtual-image.c:216
(process:17261): libfprint-virtual_device_connection-DEBUG: 04:23:37.880: 38977917478060: ../libfprint/drivers/virtual-device-listener.c:153
(process:17261): libfprint-image_device-DEBUG: 04:23:37.994: Image device open completed
(process:17261): libfprint-device-DEBUG: 04:23:37.994: Device reported open completion
(process:17261): libfprint-device-DEBUG: 04:23:37.994: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17261): libfprint-device-DEBUG: 04:23:37.995: Updated temperature model after 0.18 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17261): libfprint-device-DEBUG: 04:23:38.023: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17261): libfprint-image_device-DEBUG: 04:23:38.023: Activating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:38.023: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:38.024: Image device activation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:38.024: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.024: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:38.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-virtual_device_connection-DEBUG: 04:23:38.027: Got a new connection!
(process:17261): libfprint-virtual_image-DEBUG: 04:23:38.030: image data: 0x1f4dcd0
(process:17261): libfprint-device-DEBUG: 04:23:38.035: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:38.035: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:38.036: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.036: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:38.036: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:38.036: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-device-DEBUG: 04:23:38.037: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.037: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:38.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-device-DEBUG: 04:23:38.123: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17261): libfprint-image-DEBUG: 04:23:38.210: Minutiae scan completed in 0.172075 secs
(process:17261): libfprint-device-DEBUG: 04:23:38.211: Device reported enroll progress, reported 1 of 5 have been completed
(process:17261): libfprint-image_device-DEBUG: 04:23:38.211: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:38.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-device-DEBUG: 04:23:38.215: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:38.215: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:38.215: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-virtual_image-DEBUG: 04:23:38.217: image data: 0x1f4dcd0
(process:17261): libfprint-image_device-DEBUG: 04:23:38.223: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:38.223: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:38.224: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image-DEBUG: 04:23:38.393: Minutiae scan completed in 0.166649 secs
(process:17261): libfprint-device-DEBUG: 04:23:38.393: Device reported enroll progress, reported 2 of 5 have been completed
(process:17261): libfprint-device-DEBUG: 04:23:38.395: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.395: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:38.395: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.395: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:38.396: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-virtual_image-DEBUG: 04:23:38.400: image data: 0x1f4dcd0
(process:17261): libfprint-device-DEBUG: 04:23:38.401: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:38.401: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:38.402: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.406: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:38.406: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:38.406: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-device-DEBUG: 04:23:38.407: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.407: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:38.407: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image-DEBUG: 04:23:38.565: Minutiae scan completed in 0.155147 secs
(process:17261): libfprint-device-DEBUG: 04:23:38.566: Device reported enroll progress, reported 3 of 5 have been completed
(process:17261): libfprint-image_device-DEBUG: 04:23:38.566: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:38.566: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-virtual_image-DEBUG: 04:23:38.568: image data: 0x1f4dcd0
(process:17261): libfprint-device-DEBUG: 04:23:38.570: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:38.570: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:38.570: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.570: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:38.570: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:38.571: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-device-DEBUG: 04:23:38.571: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.571: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:38.571: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image-DEBUG: 04:23:38.691: Minutiae scan completed in 0.116845 secs
(process:17261): libfprint-device-DEBUG: 04:23:38.692: Device reported enroll progress, reported 4 of 5 have been completed
(process:17261): libfprint-image_device-DEBUG: 04:23:38.692: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:38.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-virtual_image-DEBUG: 04:23:38.694: image data: 0x1f4dcd0
(process:17261): libfprint-device-DEBUG: 04:23:38.695: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:38.696: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:38.696: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.696: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:38.696: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:38.697: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-device-DEBUG: 04:23:38.697: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.697: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:38.697: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image-DEBUG: 04:23:38.801: Minutiae scan completed in 0.101549 secs
(process:17261): libfprint-device-DEBUG: 04:23:38.802: Device reported enroll progress, reported 5 of 5 have been completed
(process:17261): libfprint-image_device-DEBUG: 04:23:38.803: Deactivating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:38.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:38.803: Image device deactivation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:38.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17261): libfprint-device-DEBUG: 04:23:38.803: Device reported enroll completion
(process:17261): libfprint-device-DEBUG: 04:23:38.804: Print for finger FP_FINGER_LEFT_THUMB enrolled
(process:17261): libfprint-device-DEBUG: 04:23:38.804: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17261): libfprint-device-DEBUG: 04:23:38.804: Updated temperature model after 0.68 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-device-DEBUG: 04:23:38.811: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-image_device-DEBUG: 04:23:38.811: Activating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:38.811: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:38.812: Image device activation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:38.812: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.812: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:38.812: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-virtual_image-DEBUG: 04:23:38.813: image data: 0x1f4ec30
(process:17261): libfprint-device-DEBUG: 04:23:38.819: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:38.819: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:38.819: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.822: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:38.822: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:38.823: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-device-DEBUG: 04:23:38.823: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:38.824: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:38.824: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image-DEBUG: 04:23:38.983: Minutiae scan completed in 0.160197 secs
(process:17261): libfprint-device-DEBUG: 04:23:39.002: Device reported enroll progress, reported 1 of 5 have been completed
(process:17261): libfprint-image_device-DEBUG: 04:23:39.003: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:39.003: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-device-DEBUG: 04:23:39.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:39.007: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:39.007: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-virtual_image-DEBUG: 04:23:39.009: image data: 0x1f4ec30
(process:17261): libfprint-image_device-DEBUG: 04:23:39.015: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:39.038: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:39.038: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image-DEBUG: 04:23:39.159: Minutiae scan completed in 0.142906 secs
(process:17261): libfprint-device-DEBUG: 04:23:39.159: Device reported enroll progress, reported 2 of 5 have been completed
(process:17261): libfprint-device-DEBUG: 04:23:39.161: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.161: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:39.161: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.161: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:39.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-virtual_image-DEBUG: 04:23:39.170: image data: 0x1f6cc40
(process:17261): libfprint-device-DEBUG: 04:23:39.172: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:39.172: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:39.172: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.173: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:39.174: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:39.174: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-device-DEBUG: 04:23:39.175: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.175: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:39.176: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image-DEBUG: 04:23:39.319: Minutiae scan completed in 0.145640 secs
(process:17261): libfprint-device-DEBUG: 04:23:39.321: Device reported enroll progress, reported 3 of 5 have been completed
(process:17261): libfprint-image_device-DEBUG: 04:23:39.322: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:39.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-virtual_image-DEBUG: 04:23:39.324: image data: 0x1f4ff00
(process:17261): libfprint-device-DEBUG: 04:23:39.326: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:39.327: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:39.327: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.328: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:39.354: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:39.354: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-device-DEBUG: 04:23:39.354: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.354: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:39.354: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image-DEBUG: 04:23:39.469: Minutiae scan completed in 0.140650 secs
(process:17261): libfprint-device-DEBUG: 04:23:39.470: Device reported enroll progress, reported 4 of 5 have been completed
(process:17261): libfprint-image_device-DEBUG: 04:23:39.470: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:39.470: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-virtual_image-DEBUG: 04:23:39.472: image data: 0x1f4ff00
(process:17261): libfprint-device-DEBUG: 04:23:39.473: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:39.473: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:39.473: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.474: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:39.474: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:39.474: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-device-DEBUG: 04:23:39.474: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.474: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:39.475: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image-DEBUG: 04:23:39.597: Minutiae scan completed in 0.120795 secs
(process:17261): libfprint-device-DEBUG: 04:23:39.606: Device reported enroll progress, reported 5 of 5 have been completed
(process:17261): libfprint-image_device-DEBUG: 04:23:39.607: Deactivating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:39.607: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:39.607: Image device deactivation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:39.607: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17261): libfprint-device-DEBUG: 04:23:39.607: Device reported enroll completion
(process:17261): libfprint-device-DEBUG: 04:23:39.607: Print for finger FP_FINGER_LEFT_THUMB enrolled
(process:17261): libfprint-device-DEBUG: 04:23:39.608: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17261): libfprint-device-DEBUG: 04:23:39.608: Updated temperature model after 0.80 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-device-DEBUG: 04:23:39.611: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-image_device-DEBUG: 04:23:39.611: Activating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:39.611: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:39.612: Image device activation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:39.612: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.612: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:39.612: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-virtual_image-DEBUG: 04:23:39.613: image data: 0x1f50c38
(process:17261): libfprint-device-DEBUG: 04:23:39.615: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:39.615: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:39.615: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.616: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:39.616: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:39.616: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-device-DEBUG: 04:23:39.617: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.617: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:39.618: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image_device-DEBUG: 04:23:39.618: Deactivating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:39.619: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:39.619: Image device deactivation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:39.619: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17261): libfprint-image-DEBUG: 04:23:39.769: Minutiae scan completed in 0.151154 secs
(process:17261): libfprint-print-DEBUG: 04:23:39.816: score 10/40
(process:17261): libfprint-print-DEBUG: 04:23:39.850: score 10/40
(process:17261): libfprint-print-DEBUG: 04:23:39.884: score 10/40
(process:17261): libfprint-print-DEBUG: 04:23:39.918: score 10/40
(process:17261): libfprint-print-DEBUG: 04:23:39.956: score 10/40
(process:17261): libfprint-print-DEBUG: 04:23:41.096: score 855/40
(process:17261): libfprint-device-DEBUG: 04:23:41.096: Device reported identify result
(process:17261): libfprint-device-DEBUG: 04:23:41.096: Device reported identify completion
(process:17261): libfprint-device-DEBUG: 04:23:41.097: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17261): libfprint-device-DEBUG: 04:23:41.097: Updated temperature model after 1.49 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-device-DEBUG: 04:23:41.103: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-image_device-DEBUG: 04:23:41.103: Activating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:41.103: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:41.104: Image device activation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:41.104: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image_device-DEBUG: 04:23:41.104: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:41.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-virtual_image-DEBUG: 04:23:41.105: image data: 0x1f4fcd8
(process:17261): libfprint-device-DEBUG: 04:23:41.107: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-image_device-DEBUG: 04:23:41.107: Image device reported finger status: on
(process:17261): libfprint-image_device-DEBUG: 04:23:41.108: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17261): libfprint-image_device-DEBUG: 04:23:41.108: Image device captured an image
(process:17261): libfprint-image_device-DEBUG: 04:23:41.134: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17261): libfprint-device-DEBUG: 04:23:41.134: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17261): libfprint-device-DEBUG: 04:23:41.134: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-image_device-DEBUG: 04:23:41.134: Image device reported finger status: off
(process:17261): libfprint-image_device-DEBUG: 04:23:41.134: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image_device-DEBUG: 04:23:41.135: Deactivating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:41.135: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:41.135: Image device deactivation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:41.135: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17261): libfprint-image-DEBUG: 04:23:41.256: Minutiae scan completed in 0.147525 secs
(process:17261): libfprint-print-DEBUG: 04:23:46.272: score 1093/40
(process:17261): libfprint-device-DEBUG: 04:23:46.273: Device reported identify result
(process:17261): libfprint-device-DEBUG: 04:23:46.273: Device reported identify completion
(process:17261): libfprint-device-DEBUG: 04:23:46.274: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17261): libfprint-device-DEBUG: 04:23:46.275: Updated temperature model after 5.17 seconds, ratio 0.28 -> 0.30, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-device-DEBUG: 04:23:46.277: Updated temperature model after 0.00 seconds, ratio 0.30 -> 0.30, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-image_device-DEBUG: 04:23:46.278: Activating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:46.278: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:46.279: Image device activation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:46.279: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image_device-DEBUG: 04:23:46.280: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:46.280: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-device-DEBUG: 04:23:46.282: Device reported identify result
(process:17261): libfprint-image_device-DEBUG: 04:23:46.282: Deactivating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:46.283: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:46.283: Image device deactivation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:46.284: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17261): libfprint-device-DEBUG: 04:23:46.284: Device reported identify completion
(process:17261): libfprint-device-DEBUG: 04:23:46.285: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-device-DEBUG: 04:23:46.287: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17261): libfprint-device-DEBUG: 04:23:46.288: Updated temperature model after 0.01 seconds, ratio 0.30 -> 0.30, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-device-DEBUG: 04:23:46.289: Updated temperature model after 0.00 seconds, ratio 0.30 -> 0.30, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-image_device-DEBUG: 04:23:46.290: Activating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:46.291: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:46.291: Image device activation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:46.292: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17261): libfprint-image_device-DEBUG: 04:23:46.292: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17261): libfprint-device-DEBUG: 04:23:46.293: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17261): libfprint-image_device-DEBUG: 04:23:46.295: Deactivating image device
(process:17261): libfprint-image_device-DEBUG: 04:23:46.295: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17261): libfprint-image_device-DEBUG: 04:23:46.296: Image device deactivation completed
(process:17261): libfprint-image_device-DEBUG: 04:23:46.296: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17261): libfprint-device-DEBUG: 04:23:46.297: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY
(process:17261): libfprint-device-DEBUG: 04:23:46.297: Device reported identify completion
(process:17261): libfprint-device-DEBUG: 04:23:46.298: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17261): libfprint-device-DEBUG: 04:23:46.300: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17261): libfprint-device-DEBUG: 04:23:46.301: Updated temperature model after 0.01 seconds, ratio 0.30 -> 0.30, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17261): libfprint-virtual_image-DEBUG: 04:23:46.303: 38977925900787: ../libfprint/drivers/virtual-image.c:244
(process:17261): libfprint-image_device-DEBUG: 04:23:46.402: Image device close completed
(process:17261): libfprint-device-DEBUG: 04:23:46.403: Device reported close completion
(process:17261): libfprint-device-DEBUG: 04:23:46.403: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17261): libfprint-device-DEBUG: 04:23:46.404: Updated temperature model after 0.10 seconds, ratio 0.30 -> 0.30, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Enroll done
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Enroll done
Identify finished
Identify finished
Identify finished
fp - device - retry - quark: The swipe was too short, please try again. (1)
Identify finished
fp - device - error - quark: An unspecified error occurred! (0)
ok
----------------------------------------------------------------------
Ran 1 test in 8.694s
OK
==============================================================================
=================================== 14/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_device_sleep
start time: 04:23:45
duration: 1.52s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb MALLOC_PERTURB_=38 G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_device_sleep
----------------------------------- stdout -----------------------------------
(process:17328): libfprint-context-DEBUG: 04:23:46.351: Initializing FpContext (libfprint version 1.94.6)
(process:17328): libfprint-context-DEBUG: 04:23:46.415: No driver found for USB device 1D6B:0003
(process:17328): libfprint-context-DEBUG: 04:23:46.415: No driver found for USB device 0BDA:5401
(process:17328): libfprint-context-DEBUG: 04:23:46.415: No driver found for USB device 1D6B:0002
(process:17328): libfprint-context-DEBUG: 04:23:46.415: No driver found for USB device 1D6B:0003
(process:17328): libfprint-context-DEBUG: 04:23:46.415: No driver found for USB device 0624:0249
(process:17328): libfprint-context-DEBUG: 04:23:46.416: No driver found for USB device 0624:0248
(process:17328): libfprint-context-DEBUG: 04:23:46.416: No driver found for USB device 1D6B:0002
(process:17328): libfprint-context-DEBUG: 04:23:46.416: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-cnsnwee0/virtual-device.socket
(process:17328): libfprint-context-DEBUG: 04:23:46.417: created
(process:17328): libfprint-device-DEBUG: 04:23:46.462: Device reported probe completion
(process:17328): libfprint-device-DEBUG: 04:23:46.462: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17328): libfprint-device-DEBUG: 04:23:46.463: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:17328): libfprint-virtual_device-DEBUG: 04:23:46.466: 38977926063887: ../libfprint/drivers/virtual-device.c:387
(process:17328): libfprint-virtual_device_connection-DEBUG: 04:23:46.479: 38977926077374: ../libfprint/drivers/virtual-device-listener.c:153
(process:17328): libfprint-device-DEBUG: 04:23:46.490: Device reported open completion
(process:17328): libfprint-device-DEBUG: 04:23:46.491: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17328): libfprint-device-DEBUG: 04:23:46.491: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17328): libfprint-virtual_device_connection-DEBUG: 04:23:46.502: Got a new connection!
(process:17328): libfprint-virtual_device-DEBUG: 04:23:46.504: Got instructions of length 10
(process:17328): libfprint-virtual_device-DEBUG: 04:23:46.504: Received command SLEEP 1500
(process:17328): libfprint-device-DEBUG: 04:23:46.528: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17328): libfprint-virtual_device-DEBUG: 04:23:46.529: Processing command SLEEP 1500
(process:17328): libfprint-virtual_device-DEBUG: 04:23:46.529: Sleeping 1500ms
(process:17328): libfprint-device-DEBUG: 04:23:46.646: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17328): libfprint-device-DEBUG: 04:23:46.834: Idle cancelling on ongoing operation!
(process:17328): libfprint-virtual_device-DEBUG: 04:23:46.834: Got cancellation!
(process:17328): libfprint-device-DEBUG: 04:23:46.835: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17328): libfprint-virtual_device-DEBUG: 04:23:46.835: Virtual device scan failed with error: Operation was cancelled
(process:17328): libfprint-device-DEBUG: 04:23:46.835: Device reported verify completion
(process:17328): libfprint-device-DEBUG: 04:23:46.835: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17328): libfprint-device-DEBUG: 04:23:46.835: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17328): libfprint-device-DEBUG: 04:23:46.836: Updated temperature model after 0.19 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17328): libfprint-virtual_device_connection-DEBUG: 04:23:47.036: Got a new connection!
(process:17328): libfprint-virtual_device-DEBUG: 04:23:47.037: Got instructions of length 16
(process:17328): libfprint-virtual_device-DEBUG: 04:23:47.037: Received command SET_KEEP_ALIVE 0
(process:17328): libfprint-virtual_device-DEBUG: 04:23:47.038: Keep alive toggled: 0
(process:17328): libfprint-virtual_device_connection-DEBUG: 04:23:47.040: Got a new connection!
(process:17328): libfprint-virtual_device-DEBUG: 04:23:47.041: Got instructions of length 19
(process:17328): libfprint-virtual_device-DEBUG: 04:23:47.042: Received command SET_ENROLL_STAGES 5
(process:17328): libfprint-device-DEBUG: 04:23:47.043: Device reported close completion
(process:17328): libfprint-device-DEBUG: 04:23:47.044: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17328): libfprint-device-DEBUG: 04:23:47.044: Updated temperature model after 0.21 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
----------------------------------------------------------------------
Ran 1 test in 0.714s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:827: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 15/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_device_sleep_before_completing_verify
start time: 04:23:46
duration: 1.57s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=22 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_device_sleep_before_completing_verify
----------------------------------- stdout -----------------------------------
(process:17333): libfprint-context-DEBUG: 04:23:46.399: Initializing FpContext (libfprint version 1.94.6)
(process:17333): libfprint-context-DEBUG: 04:23:46.428: No driver found for USB device 1D6B:0003
(process:17333): libfprint-context-DEBUG: 04:23:46.428: No driver found for USB device 0BDA:5401
(process:17333): libfprint-context-DEBUG: 04:23:46.428: No driver found for USB device 1D6B:0002
(process:17333): libfprint-context-DEBUG: 04:23:46.428: No driver found for USB device 1D6B:0003
(process:17333): libfprint-context-DEBUG: 04:23:46.429: No driver found for USB device 0624:0249
(process:17333): libfprint-context-DEBUG: 04:23:46.429: No driver found for USB device 0624:0248
(process:17333): libfprint-context-DEBUG: 04:23:46.429: No driver found for USB device 1D6B:0002
(process:17333): libfprint-context-DEBUG: 04:23:46.429: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-3e9ai57z/virtual-device.socket
(process:17333): libfprint-context-DEBUG: 04:23:46.430: created
(process:17333): libfprint-device-DEBUG: 04:23:46.441: Device reported probe completion
(process:17333): libfprint-device-DEBUG: 04:23:46.442: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17333): libfprint-device-DEBUG: 04:23:46.442: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:17333): libfprint-virtual_device-DEBUG: 04:23:46.446: 38977926044141: ../libfprint/drivers/virtual-device.c:387
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:46.448: 38977926045793: ../libfprint/drivers/virtual-device-listener.c:153
(process:17333): libfprint-device-DEBUG: 04:23:46.451: Device reported open completion
(process:17333): libfprint-device-DEBUG: 04:23:46.452: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17333): libfprint-device-DEBUG: 04:23:46.452: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:46.457: Got a new connection!
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.459: Got instructions of length 14
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.459: Received command SCAN foo-print
(process:17333): libfprint-device-DEBUG: 04:23:46.467: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.468: Processing command SCAN foo-print
(process:17333): libfprint-device-DEBUG: 04:23:46.468: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17333): libfprint-device-DEBUG: 04:23:46.468: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17333): libfprint-device-DEBUG: 04:23:46.469: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17333): libfprint-device-DEBUG: 04:23:46.469: Device reported enroll progress, reported 1 of 5 have been completed
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.471: Sleeping completed
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:46.472: Got a new connection!
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.474: Got instructions of length 14
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.474: Received command SCAN foo-print
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.474: Processing command SCAN foo-print
(process:17333): libfprint-device-DEBUG: 04:23:46.475: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17333): libfprint-device-DEBUG: 04:23:46.475: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17333): libfprint-device-DEBUG: 04:23:46.476: Device reported enroll progress, reported 2 of 5 have been completed
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.477: Sleeping completed
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:46.480: Got a new connection!
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.481: Got instructions of length 14
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.482: Received command SCAN foo-print
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.482: Processing command SCAN foo-print
(process:17333): libfprint-device-DEBUG: 04:23:46.483: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17333): libfprint-device-DEBUG: 04:23:46.483: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17333): libfprint-device-DEBUG: 04:23:46.484: Device reported enroll progress, reported 3 of 5 have been completed
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.485: Sleeping completed
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:46.487: Got a new connection!
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.488: Got instructions of length 14
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.489: Received command SCAN foo-print
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.489: Processing command SCAN foo-print
(process:17333): libfprint-device-DEBUG: 04:23:46.489: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17333): libfprint-device-DEBUG: 04:23:46.490: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17333): libfprint-device-DEBUG: 04:23:46.490: Device reported enroll progress, reported 4 of 5 have been completed
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.492: Sleeping completed
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:46.494: Got a new connection!
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.496: Got instructions of length 14
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.496: Received command SCAN foo-print
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.496: Processing command SCAN foo-print
(process:17333): libfprint-device-DEBUG: 04:23:46.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17333): libfprint-device-DEBUG: 04:23:46.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17333): libfprint-device-DEBUG: 04:23:46.498: Device reported enroll progress, reported 5 of 5 have been completed
(process:17333): libfprint-device-DEBUG: 04:23:46.498: Device reported enroll completion
(process:17333): libfprint-device-DEBUG: 04:23:46.499: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17333): libfprint-device-DEBUG: 04:23:46.499: Print for finger FP_FINGER_LEFT_RING enrolled
(process:17333): libfprint-device-DEBUG: 04:23:46.501: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17333): libfprint-device-DEBUG: 04:23:46.501: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:46.508: Got a new connection!
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.510: Got instructions of length 9
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.510: Received command SLEEP 100
(process:17333): libfprint-device-DEBUG: 04:23:46.515: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.516: Processing command SLEEP 100
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.516: Sleeping 100ms
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:46.518: Got a new connection!
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.519: Got instructions of length 14
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.520: Received command SCAN bar-print
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:46.522: Got a new connection!
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.523: Got instructions of length 9
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.524: Received command SLEEP 800
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.617: Sleeping completed
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.617: Processing command SCAN bar-print
(process:17333): libfprint-device-DEBUG: 04:23:46.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17333): libfprint-device-DEBUG: 04:23:46.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.619: Virtual device scanned print bar-print
(process:17333): libfprint-device-DEBUG: 04:23:46.619: Device reported verify result
(process:17333): libfprint-device-DEBUG: 04:23:46.620: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.620: Processing command SLEEP 800
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.621: Sleeping 800ms
(process:17333): libfprint-virtual_device-DEBUG: 04:23:46.621: Sleeping now, command queued for later: SCAN bar-print
(process:17333): libfprint-virtual_device-DEBUG: 04:23:47.422: Sleeping completed
(process:17333): libfprint-virtual_device-DEBUG: 04:23:47.422: Processing command SCAN bar-print
(process:17333): libfprint-device-DEBUG: 04:23:47.422: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17333): libfprint-virtual_device-DEBUG: 04:23:47.422: Virtual device scanned print bar-print
(process:17333): libfprint-device-DEBUG: 04:23:47.423: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17333): libfprint-device-DEBUG: 04:23:47.423: Device reported verify completion
(process:17333): libfprint-device-DEBUG: 04:23:47.423: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17333): libfprint-device-DEBUG: 04:23:47.423: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17333): libfprint-device-DEBUG: 04:23:47.424: Updated temperature model after 0.91 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:47.426: Got a new connection!
(process:17333): libfprint-virtual_device-DEBUG: 04:23:47.427: Got instructions of length 16
(process:17333): libfprint-virtual_device-DEBUG: 04:23:47.427: Received command SET_KEEP_ALIVE 0
(process:17333): libfprint-virtual_device-DEBUG: 04:23:47.427: Keep alive toggled: 0
(process:17333): libfprint-virtual_device_connection-DEBUG: 04:23:47.429: Got a new connection!
(process:17333): libfprint-virtual_device-DEBUG: 04:23:47.438: Got instructions of length 19
(process:17333): libfprint-virtual_device-DEBUG: 04:23:47.438: Received command SET_ENROLL_STAGES 5
(process:17333): libfprint-device-DEBUG: 04:23:47.440: Device reported close completion
(process:17333): libfprint-device-DEBUG: 04:23:47.440: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17333): libfprint-device-DEBUG: 04:23:47.441: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17333): libfprint-virtual_device-DEBUG: 04:23:47.451: 38977927049259: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 1.063s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:865: DeprecationWarning: FPrint.Device.supports_identify is deprecated
self.start_verify(enrolled, identify=self.dev.supports_identify())
==============================================================================
=================================== 16/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll
start time: 04:23:47
duration: 0.62s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=77 UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_enroll
----------------------------------- stdout -----------------------------------
(process:17346): libfprint-context-DEBUG: 04:23:47.475: Initializing FpContext (libfprint version 1.94.6)
(process:17346): libfprint-context-DEBUG: 04:23:47.508: No driver found for USB device 1D6B:0003
(process:17346): libfprint-context-DEBUG: 04:23:47.508: No driver found for USB device 0BDA:5401
(process:17346): libfprint-context-DEBUG: 04:23:47.509: No driver found for USB device 1D6B:0002
(process:17346): libfprint-context-DEBUG: 04:23:47.509: No driver found for USB device 1D6B:0003
(process:17346): libfprint-context-DEBUG: 04:23:47.510: No driver found for USB device 0624:0249
(process:17346): libfprint-context-DEBUG: 04:23:47.510: No driver found for USB device 0624:0248
(process:17346): libfprint-context-DEBUG: 04:23:47.511: No driver found for USB device 1D6B:0002
(process:17346): libfprint-context-DEBUG: 04:23:47.511: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-unw_5eqn/virtual-device.socket
(process:17346): libfprint-context-DEBUG: 04:23:47.513: created
(process:17346): libfprint-device-DEBUG: 04:23:47.530: Device reported probe completion
(process:17346): libfprint-device-DEBUG: 04:23:47.531: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17346): libfprint-device-DEBUG: 04:23:47.532: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll (__main__.VirtualDevice.test_enroll) ... (process:17346): libfprint-virtual_device-DEBUG: 04:23:47.535: 38977927133518: ../libfprint/drivers/virtual-device.c:387
(process:17346): libfprint-virtual_device_connection-DEBUG: 04:23:47.537: 38977927135346: ../libfprint/drivers/virtual-device-listener.c:153
(process:17346): libfprint-device-DEBUG: 04:23:47.541: Device reported open completion
(process:17346): libfprint-device-DEBUG: 04:23:47.541: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17346): libfprint-device-DEBUG: 04:23:47.542: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17346): libfprint-virtual_device_connection-DEBUG: 04:23:47.547: Got a new connection!
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.550: Got instructions of length 14
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.550: Received command SCAN testprint
(process:17346): libfprint-device-DEBUG: 04:23:47.557: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.558: Processing command SCAN testprint
(process:17346): libfprint-device-DEBUG: 04:23:47.558: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17346): libfprint-device-DEBUG: 04:23:47.559: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17346): libfprint-device-DEBUG: 04:23:47.559: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17346): libfprint-device-DEBUG: 04:23:47.560: Device reported enroll progress, reported 1 of 5 have been completed
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.561: Sleeping completed
(process:17346): libfprint-virtual_device_connection-DEBUG: 04:23:47.563: Got a new connection!
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.564: Got instructions of length 14
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.565: Received command SCAN testprint
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.565: Processing command SCAN testprint
(process:17346): libfprint-device-DEBUG: 04:23:47.566: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17346): libfprint-device-DEBUG: 04:23:47.566: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17346): libfprint-device-DEBUG: 04:23:47.567: Device reported enroll progress, reported 2 of 5 have been completed
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.568: Sleeping completed
(process:17346): libfprint-virtual_device_connection-DEBUG: 04:23:47.570: Got a new connection!
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.572: Got instructions of length 14
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.572: Received command SCAN testprint
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.573: Processing command SCAN testprint
(process:17346): libfprint-device-DEBUG: 04:23:47.573: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17346): libfprint-device-DEBUG: 04:23:47.574: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17346): libfprint-device-DEBUG: 04:23:47.574: Device reported enroll progress, reported 3 of 5 have been completed
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.575: Sleeping completed
(process:17346): libfprint-virtual_device_connection-DEBUG: 04:23:47.578: Got a new connection!
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.579: Got instructions of length 14
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.580: Received command SCAN testprint
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.580: Processing command SCAN testprint
(process:17346): libfprint-device-DEBUG: 04:23:47.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17346): libfprint-device-DEBUG: 04:23:47.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17346): libfprint-device-DEBUG: 04:23:47.582: Device reported enroll progress, reported 4 of 5 have been completed
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.583: Sleeping completed
(process:17346): libfprint-virtual_device_connection-DEBUG: 04:23:47.585: Got a new connection!
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.587: Got instructions of length 14
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.587: Received command SCAN testprint
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.588: Processing command SCAN testprint
(process:17346): libfprint-device-DEBUG: 04:23:47.588: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17346): libfprint-device-DEBUG: 04:23:47.589: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17346): libfprint-device-DEBUG: 04:23:47.589: Device reported enroll progress, reported 5 of 5 have been completed
(process:17346): libfprint-device-DEBUG: 04:23:47.590: Device reported enroll completion
(process:17346): libfprint-device-DEBUG: 04:23:47.590: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17346): libfprint-device-DEBUG: 04:23:47.591: Print for finger FP_FINGER_LEFT_LITTLE enrolled
(process:17346): libfprint-device-DEBUG: 04:23:47.592: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17346): libfprint-device-DEBUG: 04:23:47.593: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17346): libfprint-virtual_device_connection-DEBUG: 04:23:47.608: Got a new connection!
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.609: Got instructions of length 16
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.610: Received command SET_KEEP_ALIVE 0
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.610: Keep alive toggled: 0
(process:17346): libfprint-virtual_device_connection-DEBUG: 04:23:47.612: Got a new connection!
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.614: Got instructions of length 19
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.614: Received command SET_ENROLL_STAGES 5
(process:17346): libfprint-device-DEBUG: 04:23:47.617: Device reported close completion
(process:17346): libfprint-device-DEBUG: 04:23:47.618: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17346): libfprint-device-DEBUG: 04:23:47.619: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17346): libfprint-virtual_device-DEBUG: 04:23:47.621: 38977927219669: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.169s
OK
==============================================================================
=================================== 17/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_script
start time: 04:23:47
duration: 0.85s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=33 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_enroll_script
----------------------------------- stdout -----------------------------------
(process:17351): libfprint-context-DEBUG: 04:23:48.117: Initializing FpContext (libfprint version 1.94.6)
(process:17351): libfprint-context-DEBUG: 04:23:48.157: No driver found for USB device 1D6B:0003
(process:17351): libfprint-context-DEBUG: 04:23:48.157: No driver found for USB device 0BDA:5401
(process:17351): libfprint-context-DEBUG: 04:23:48.157: No driver found for USB device 1D6B:0002
(process:17351): libfprint-context-DEBUG: 04:23:48.158: No driver found for USB device 1D6B:0003
(process:17351): libfprint-context-DEBUG: 04:23:48.162: No driver found for USB device 0624:0249
(process:17351): libfprint-context-DEBUG: 04:23:48.162: No driver found for USB device 0624:0248
(process:17351): libfprint-context-DEBUG: 04:23:48.162: No driver found for USB device 1D6B:0002
(process:17351): libfprint-context-DEBUG: 04:23:48.162: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-zdfl9bgh/virtual-device.socket
(process:17351): libfprint-context-DEBUG: 04:23:48.164: created
(process:17351): libfprint-device-DEBUG: 04:23:48.179: Device reported probe completion
(process:17351): libfprint-device-DEBUG: 04:23:48.180: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17351): libfprint-device-DEBUG: 04:23:48.181: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:17351): libfprint-virtual_device-DEBUG: 04:23:48.188: 38977927786517: ../libfprint/drivers/virtual-device.c:387
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.190: 38977927788284: ../libfprint/drivers/virtual-device-listener.c:153
(process:17351): libfprint-device-DEBUG: 04:23:48.193: Device reported open completion
(process:17351): libfprint-device-DEBUG: 04:23:48.194: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17351): libfprint-device-DEBUG: 04:23:48.195: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.197: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.204: Got instructions of length 19
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.204: Received command SET_ENROLL_STAGES 8
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.210: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.211: Got instructions of length 13
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.211: Received command SCAN print-id
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.213: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.215: Got instructions of length 13
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.215: Received command SCAN print-id
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.219: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.220: Got instructions of length 7
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.221: Received command RETRY 1
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.223: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.225: Got instructions of length 13
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.225: Received command SCAN print-id
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.231: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.232: Got instructions of length 7
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.232: Received command RETRY 3
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.234: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.235: Got instructions of length 13
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.235: Received command SCAN print-id
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.243: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.244: Got instructions of length 7
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.244: Received command RETRY 2
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.246: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.247: Got instructions of length 13
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.247: Received command SCAN print-id
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.249: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.250: Got instructions of length 8
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.250: Received command SLEEP 10
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.252: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.253: Got instructions of length 8
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.253: Received command SLEEP 20
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.263: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.264: Got instructions of length 7
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.264: Received command RETRY 0
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.266: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.267: Got instructions of length 7
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.267: Received command RETRY 3
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.269: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.270: Got instructions of length 13
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.270: Received command SCAN print-id
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.272: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.273: Got instructions of length 15
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.273: Received command SCAN another-id
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.279: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.280: Got instructions of length 13
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.280: Received command SCAN print-id
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.281: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.283: Got instructions of length 13
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.283: Received command SCAN print-id
(process:17351): libfprint-device-DEBUG: 04:23:48.291: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.291: Processing command SCAN print-id
(process:17351): libfprint-device-DEBUG: 04:23:48.291: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17351): libfprint-device-DEBUG: 04:23:48.291: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17351): libfprint-device-DEBUG: 04:23:48.292: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17351): libfprint-device-DEBUG: 04:23:48.292: Device reported enroll progress, reported 1 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.292: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.292: Processing command SCAN print-id
(process:17351): libfprint-device-DEBUG: 04:23:48.292: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17351): libfprint-device-DEBUG: 04:23:48.292: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17351): libfprint-device-DEBUG: 04:23:48.293: Device reported enroll progress, reported 2 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.293: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.293: Processing command RETRY 1
(process:17351): libfprint-device-DEBUG: 04:23:48.293: Device reported enroll progress, reported 2 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.293: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.294: Processing command SCAN print-id
(process:17351): libfprint-device-DEBUG: 04:23:48.294: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17351): libfprint-device-DEBUG: 04:23:48.295: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17351): libfprint-device-DEBUG: 04:23:48.295: Device reported enroll progress, reported 3 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.296: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.296: Processing command RETRY 3
(process:17351): libfprint-device-DEBUG: 04:23:48.296: Device reported enroll progress, reported 3 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.297: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.297: Processing command SCAN print-id
(process:17351): libfprint-device-DEBUG: 04:23:48.297: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17351): libfprint-device-DEBUG: 04:23:48.298: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17351): libfprint-device-DEBUG: 04:23:48.298: Device reported enroll progress, reported 4 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.302: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.302: Processing command RETRY 2
(process:17351): libfprint-device-DEBUG: 04:23:48.303: Device reported enroll progress, reported 4 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.303: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.304: Processing command SCAN print-id
(process:17351): libfprint-device-DEBUG: 04:23:48.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17351): libfprint-device-DEBUG: 04:23:48.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17351): libfprint-device-DEBUG: 04:23:48.305: Device reported enroll progress, reported 5 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.305: Processing command SLEEP 10
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.306: Sleeping 10ms
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.317: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.318: Processing command SLEEP 20
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.318: Sleeping 20ms
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.342: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.343: Processing command RETRY 0
(process:17351): libfprint-device-DEBUG: 04:23:48.343: Device reported enroll progress, reported 5 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.343: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.343: Processing command RETRY 3
(process:17351): libfprint-device-DEBUG: 04:23:48.343: Device reported enroll progress, reported 5 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.344: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.344: Processing command SCAN print-id
(process:17351): libfprint-device-DEBUG: 04:23:48.344: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17351): libfprint-device-DEBUG: 04:23:48.344: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17351): libfprint-device-DEBUG: 04:23:48.344: Device reported enroll progress, reported 6 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.344: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.345: Processing command SCAN another-id
(process:17351): libfprint-device-DEBUG: 04:23:48.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17351): libfprint-device-DEBUG: 04:23:48.345: Device reported enroll progress, reported 6 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.345: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.345: Processing command SCAN print-id
(process:17351): libfprint-device-DEBUG: 04:23:48.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17351): libfprint-device-DEBUG: 04:23:48.345: Device reported enroll progress, reported 7 of 8 have been completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.346: Sleeping completed
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.346: Processing command SCAN print-id
(process:17351): libfprint-device-DEBUG: 04:23:48.346: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17351): libfprint-device-DEBUG: 04:23:48.346: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17351): libfprint-device-DEBUG: 04:23:48.346: Device reported enroll progress, reported 8 of 8 have been completed
(process:17351): libfprint-device-DEBUG: 04:23:48.346: Device reported enroll completion
(process:17351): libfprint-device-DEBUG: 04:23:48.346: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17351): libfprint-device-DEBUG: 04:23:48.347: Print for finger FP_FINGER_UNKNOWN enrolled
(process:17351): libfprint-device-DEBUG: 04:23:48.347: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17351): libfprint-device-DEBUG: 04:23:48.347: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.350: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.351: Got instructions of length 16
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.351: Received command SET_KEEP_ALIVE 0
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.351: Keep alive toggled: 0
(process:17351): libfprint-virtual_device_connection-DEBUG: 04:23:48.353: Got a new connection!
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.362: Got instructions of length 19
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.363: Received command SET_ENROLL_STAGES 5
(process:17351): libfprint-device-DEBUG: 04:23:48.364: Device reported close completion
(process:17351): libfprint-device-DEBUG: 04:23:48.365: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17351): libfprint-device-DEBUG: 04:23:48.365: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
(process:17351): libfprint-virtual_device-DEBUG: 04:23:48.367: 38977927965177: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.270s
OK
==============================================================================
=================================== 18/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_script_interactive
start time: 04:23:47
duration: 0.80s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=72 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_enroll_script_interactive
----------------------------------- stdout -----------------------------------
(process:17353): libfprint-context-DEBUG: 04:23:48.173: Initializing FpContext (libfprint version 1.94.6)
(process:17353): libfprint-context-DEBUG: 04:23:48.204: No driver found for USB device 1D6B:0003
(process:17353): libfprint-context-DEBUG: 04:23:48.204: No driver found for USB device 0BDA:5401
(process:17353): libfprint-context-DEBUG: 04:23:48.205: No driver found for USB device 1D6B:0002
(process:17353): libfprint-context-DEBUG: 04:23:48.205: No driver found for USB device 1D6B:0003
(process:17353): libfprint-context-DEBUG: 04:23:48.206: No driver found for USB device 0624:0249
(process:17353): libfprint-context-DEBUG: 04:23:48.206: No driver found for USB device 0624:0248
(process:17353): libfprint-context-DEBUG: 04:23:48.207: No driver found for USB device 1D6B:0002
(process:17353): libfprint-context-DEBUG: 04:23:48.207: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-xk7o_m3d/virtual-device.socket
(process:17353): libfprint-context-DEBUG: 04:23:48.209: created
(process:17353): libfprint-device-DEBUG: 04:23:48.220: Device reported probe completion
(process:17353): libfprint-device-DEBUG: 04:23:48.221: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17353): libfprint-device-DEBUG: 04:23:48.221: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:17353): libfprint-virtual_device-DEBUG: 04:23:48.224: 38977927822141: ../libfprint/drivers/virtual-device.c:387
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.226: 38977927824285: ../libfprint/drivers/virtual-device-listener.c:153
(process:17353): libfprint-device-DEBUG: 04:23:48.229: Device reported open completion
(process:17353): libfprint-device-DEBUG: 04:23:48.230: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17353): libfprint-device-DEBUG: 04:23:48.231: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.235: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.237: Got instructions of length 8
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.238: Received command SLEEP 50
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.240: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.241: Got instructions of length 13
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.242: Received command SCAN print-id
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.245: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.246: Got instructions of length 13
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.247: Received command SCAN print-id
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.252: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.254: Got instructions of length 7
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.254: Received command RETRY 1
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.256: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.258: Got instructions of length 13
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.258: Received command SCAN print-id
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.261: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.262: Got instructions of length 8
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.263: Received command SLEEP 50
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.265: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.267: Got instructions of length 13
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.268: Received command SCAN print-id
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.271: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.273: Got instructions of length 7
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.273: Received command RETRY 2
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.275: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.277: Got instructions of length 15
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.277: Received command SCAN another-id
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.279: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.281: Got instructions of length 13
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.281: Received command SCAN print-id
(process:17353): libfprint-device-DEBUG: 04:23:48.288: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.289: Processing command SLEEP 50
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.290: Sleeping 50ms
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.342: Sleeping completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.342: Processing command SCAN print-id
(process:17353): libfprint-device-DEBUG: 04:23:48.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17353): libfprint-device-DEBUG: 04:23:48.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17353): libfprint-device-DEBUG: 04:23:48.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17353): libfprint-device-DEBUG: 04:23:48.347: Device reported enroll progress, reported 1 of 5 have been completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.348: Sleeping completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.348: Processing command SCAN print-id
(process:17353): libfprint-device-DEBUG: 04:23:48.348: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17353): libfprint-device-DEBUG: 04:23:48.348: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17353): libfprint-device-DEBUG: 04:23:48.348: Device reported enroll progress, reported 2 of 5 have been completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.349: Sleeping completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.349: Processing command RETRY 1
(process:17353): libfprint-device-DEBUG: 04:23:48.349: Device reported enroll progress, reported 2 of 5 have been completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.349: Sleeping completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.349: Processing command SCAN print-id
(process:17353): libfprint-device-DEBUG: 04:23:48.349: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17353): libfprint-device-DEBUG: 04:23:48.350: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17353): libfprint-device-DEBUG: 04:23:48.350: Device reported enroll progress, reported 3 of 5 have been completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.350: Processing command SLEEP 50
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.350: Sleeping 50ms
(process:17353): libfprint-device-DEBUG: 04:23:48.402: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.402: Sleeping completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.402: Processing command SCAN print-id
(process:17353): libfprint-device-DEBUG: 04:23:48.403: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17353): libfprint-device-DEBUG: 04:23:48.403: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17353): libfprint-device-DEBUG: 04:23:48.403: Device reported enroll progress, reported 4 of 5 have been completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.403: Sleeping completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.404: Processing command RETRY 2
(process:17353): libfprint-device-DEBUG: 04:23:48.404: Device reported enroll progress, reported 4 of 5 have been completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.404: Sleeping completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.404: Processing command SCAN another-id
(process:17353): libfprint-device-DEBUG: 04:23:48.404: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17353): libfprint-device-DEBUG: 04:23:48.405: Device reported enroll progress, reported 4 of 5 have been completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.405: Sleeping completed
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.405: Processing command SCAN print-id
(process:17353): libfprint-device-DEBUG: 04:23:48.405: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17353): libfprint-device-DEBUG: 04:23:48.405: Device reported enroll progress, reported 5 of 5 have been completed
(process:17353): libfprint-device-DEBUG: 04:23:48.406: Device reported enroll completion
(process:17353): libfprint-device-DEBUG: 04:23:48.406: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17353): libfprint-device-DEBUG: 04:23:48.406: Print for finger FP_FINGER_UNKNOWN enrolled
(process:17353): libfprint-device-DEBUG: 04:23:48.406: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17353): libfprint-device-DEBUG: 04:23:48.407: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.412: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.418: Got instructions of length 16
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.419: Received command SET_KEEP_ALIVE 0
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.419: Keep alive toggled: 0
(process:17353): libfprint-virtual_device_connection-DEBUG: 04:23:48.421: Got a new connection!
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.426: Got instructions of length 19
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.427: Received command SET_ENROLL_STAGES 5
(process:17353): libfprint-device-DEBUG: 04:23:48.429: Device reported close completion
(process:17353): libfprint-device-DEBUG: 04:23:48.430: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17353): libfprint-device-DEBUG: 04:23:48.430: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
(process:17353): libfprint-virtual_device-DEBUG: 04:23:48.433: 38977928030903: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.272s
OK
==============================================================================
=================================== 19/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_device_sleep_on_cancellation
start time: 04:23:46
duration: 2.10s
result: exit status 0
command: MALLOC_PERTURB_=56 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_device_sleep_on_cancellation
----------------------------------- stdout -----------------------------------
(process:17341): libfprint-context-DEBUG: 04:23:46.950: Initializing FpContext (libfprint version 1.94.6)
(process:17341): libfprint-context-DEBUG: 04:23:46.982: No driver found for USB device 1D6B:0003
(process:17341): libfprint-context-DEBUG: 04:23:46.982: No driver found for USB device 0BDA:5401
(process:17341): libfprint-context-DEBUG: 04:23:46.983: No driver found for USB device 1D6B:0002
(process:17341): libfprint-context-DEBUG: 04:23:46.983: No driver found for USB device 1D6B:0003
(process:17341): libfprint-context-DEBUG: 04:23:46.984: No driver found for USB device 0624:0249
(process:17341): libfprint-context-DEBUG: 04:23:46.984: No driver found for USB device 0624:0248
(process:17341): libfprint-context-DEBUG: 04:23:46.985: No driver found for USB device 1D6B:0002
(process:17341): libfprint-context-DEBUG: 04:23:46.985: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-o_zf5hsj/virtual-device.socket
(process:17341): libfprint-context-DEBUG: 04:23:46.987: created
(process:17341): libfprint-device-DEBUG: 04:23:46.999: Device reported probe completion
(process:17341): libfprint-device-DEBUG: 04:23:47.001: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17341): libfprint-device-DEBUG: 04:23:47.001: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:17341): libfprint-virtual_device-DEBUG: 04:23:47.005: 38977926603024: ../libfprint/drivers/virtual-device.c:387
(process:17341): libfprint-virtual_device_connection-DEBUG: 04:23:47.007: 38977926604824: ../libfprint/drivers/virtual-device-listener.c:153
(process:17341): libfprint-device-DEBUG: 04:23:47.010: Device reported open completion
(process:17341): libfprint-device-DEBUG: 04:23:47.011: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17341): libfprint-device-DEBUG: 04:23:47.011: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17341): libfprint-virtual_device_connection-DEBUG: 04:23:47.015: Got a new connection!
(process:17341): libfprint-virtual_device-DEBUG: 04:23:47.017: Got instructions of length 26
(process:17341): libfprint-virtual_device-DEBUG: 04:23:47.017: Received command SET_CANCELLATION_ENABLED 0
(process:17341): libfprint-virtual_device-DEBUG: 04:23:47.018: Cancellation support toggled: 0
(process:17341): libfprint-virtual_device_connection-DEBUG: 04:23:47.020: Got a new connection!
(process:17341): libfprint-virtual_device-DEBUG: 04:23:47.021: Got instructions of length 10
(process:17341): libfprint-virtual_device-DEBUG: 04:23:47.022: Received command SLEEP 1500
(process:17341): libfprint-virtual_device_connection-DEBUG: 04:23:47.024: Got a new connection!
(process:17341): libfprint-virtual_device-DEBUG: 04:23:47.025: Got instructions of length 14
(process:17341): libfprint-virtual_device-DEBUG: 04:23:47.026: Received command SCAN foo-print
(process:17341): libfprint-device-DEBUG: 04:23:47.035: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17341): libfprint-virtual_device-DEBUG: 04:23:47.035: Processing command SLEEP 1500
(process:17341): libfprint-virtual_device-DEBUG: 04:23:47.036: Sleeping 1500ms
(process:17341): libfprint-device-DEBUG: 04:23:47.140: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17341): libfprint-device-DEBUG: 04:23:47.338: Idle cancelling on ongoing operation!
(process:17341): libfprint-virtual_device-DEBUG: 04:23:48.542: Sleeping completed
(process:17341): libfprint-device-DEBUG: 04:23:48.542: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17341): libfprint-virtual_device-DEBUG: 04:23:48.542: Virtual device scan failed with error: Operation was cancelled
(process:17341): libfprint-device-DEBUG: 04:23:48.542: Device reported verify completion
(process:17341): libfprint-device-DEBUG: 04:23:48.543: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17341): libfprint-device-DEBUG: 04:23:48.543: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17341): libfprint-device-DEBUG: 04:23:48.543: Updated temperature model after 1.40 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17341): libfprint-virtual_device-DEBUG: 04:23:48.548: Processing command SCAN foo-print
(process:17341): libfprint-device-DEBUG: 04:23:48.548: Device reported close completion
(process:17341): libfprint-device-DEBUG: 04:23:48.548: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17341): libfprint-device-DEBUG: 04:23:48.549: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
----------------------------------------------------------------------
Ran 1 test in 1.622s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:844: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 20/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_verify_match
start time: 04:23:48
duration: 0.78s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=205 FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_enroll_verify_match
----------------------------------- stdout -----------------------------------
(process:17363): libfprint-context-DEBUG: 04:23:49.006: Initializing FpContext (libfprint version 1.94.6)
(process:17363): libfprint-context-DEBUG: 04:23:49.045: No driver found for USB device 1D6B:0003
(process:17363): libfprint-context-DEBUG: 04:23:49.046: No driver found for USB device 0BDA:5401
(process:17363): libfprint-context-DEBUG: 04:23:49.047: No driver found for USB device 1D6B:0002
(process:17363): libfprint-context-DEBUG: 04:23:49.047: No driver found for USB device 1D6B:0003
(process:17363): libfprint-context-DEBUG: 04:23:49.048: No driver found for USB device 0624:0249
(process:17363): libfprint-context-DEBUG: 04:23:49.048: No driver found for USB device 0624:0248
(process:17363): libfprint-context-DEBUG: 04:23:49.049: No driver found for USB device 1D6B:0002
(process:17363): libfprint-context-DEBUG: 04:23:49.049: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-ea0rcohx/virtual-device.socket
(process:17363): libfprint-context-DEBUG: 04:23:49.053: created
(process:17363): libfprint-device-DEBUG: 04:23:49.067: Device reported probe completion
(process:17363): libfprint-device-DEBUG: 04:23:49.067: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17363): libfprint-device-DEBUG: 04:23:49.067: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:17363): libfprint-virtual_device-DEBUG: 04:23:49.070: 38977928668725: ../libfprint/drivers/virtual-device.c:387
(process:17363): libfprint-virtual_device_connection-DEBUG: 04:23:49.072: 38977928670111: ../libfprint/drivers/virtual-device-listener.c:153
(process:17363): libfprint-device-DEBUG: 04:23:49.075: Device reported open completion
(process:17363): libfprint-device-DEBUG: 04:23:49.075: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17363): libfprint-device-DEBUG: 04:23:49.076: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17363): libfprint-virtual_device_connection-DEBUG: 04:23:49.080: Got a new connection!
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.082: Got instructions of length 14
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.082: Received command SCAN testprint
(process:17363): libfprint-device-DEBUG: 04:23:49.089: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.090: Processing command SCAN testprint
(process:17363): libfprint-device-DEBUG: 04:23:49.090: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17363): libfprint-device-DEBUG: 04:23:49.091: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17363): libfprint-device-DEBUG: 04:23:49.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17363): libfprint-device-DEBUG: 04:23:49.093: Device reported enroll progress, reported 1 of 5 have been completed
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.095: Sleeping completed
(process:17363): libfprint-virtual_device_connection-DEBUG: 04:23:49.097: Got a new connection!
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.098: Got instructions of length 14
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.099: Received command SCAN testprint
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.099: Processing command SCAN testprint
(process:17363): libfprint-device-DEBUG: 04:23:49.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17363): libfprint-device-DEBUG: 04:23:49.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17363): libfprint-device-DEBUG: 04:23:49.101: Device reported enroll progress, reported 2 of 5 have been completed
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.102: Sleeping completed
(process:17363): libfprint-virtual_device_connection-DEBUG: 04:23:49.106: Got a new connection!
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.107: Got instructions of length 14
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.108: Received command SCAN testprint
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.108: Processing command SCAN testprint
(process:17363): libfprint-device-DEBUG: 04:23:49.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17363): libfprint-device-DEBUG: 04:23:49.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17363): libfprint-device-DEBUG: 04:23:49.110: Device reported enroll progress, reported 3 of 5 have been completed
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.111: Sleeping completed
(process:17363): libfprint-virtual_device_connection-DEBUG: 04:23:49.114: Got a new connection!
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.116: Got instructions of length 14
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.116: Received command SCAN testprint
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.117: Processing command SCAN testprint
(process:17363): libfprint-device-DEBUG: 04:23:49.118: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17363): libfprint-device-DEBUG: 04:23:49.118: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17363): libfprint-device-DEBUG: 04:23:49.119: Device reported enroll progress, reported 4 of 5 have been completed
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.121: Sleeping completed
(process:17363): libfprint-virtual_device_connection-DEBUG: 04:23:49.123: Got a new connection!
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.125: Got instructions of length 14
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.125: Received command SCAN testprint
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.126: Processing command SCAN testprint
(process:17363): libfprint-device-DEBUG: 04:23:49.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17363): libfprint-device-DEBUG: 04:23:49.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17363): libfprint-device-DEBUG: 04:23:49.128: Device reported enroll progress, reported 5 of 5 have been completed
(process:17363): libfprint-device-DEBUG: 04:23:49.128: Device reported enroll completion
(process:17363): libfprint-device-DEBUG: 04:23:49.130: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17363): libfprint-device-DEBUG: 04:23:49.130: Print for finger FP_FINGER_LEFT_THUMB enrolled
(process:17363): libfprint-device-DEBUG: 04:23:49.132: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17363): libfprint-device-DEBUG: 04:23:49.133: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17363): libfprint-virtual_device_connection-DEBUG: 04:23:49.144: Got a new connection!
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.146: Got instructions of length 14
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.147: Received command SCAN testprint
(process:17363): libfprint-device-DEBUG: 04:23:49.153: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.154: Processing command SCAN testprint
(process:17363): libfprint-device-DEBUG: 04:23:49.154: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17363): libfprint-device-DEBUG: 04:23:49.155: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.155: Virtual device scanned print testprint
(process:17363): libfprint-device-DEBUG: 04:23:49.157: Device reported verify result
(process:17363): libfprint-device-DEBUG: 04:23:49.158: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17363): libfprint-device-DEBUG: 04:23:49.158: Device reported verify completion
(process:17363): libfprint-device-DEBUG: 04:23:49.159: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17363): libfprint-device-DEBUG: 04:23:49.160: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17363): libfprint-device-DEBUG: 04:23:49.161: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17363): libfprint-virtual_device_connection-DEBUG: 04:23:49.164: Got a new connection!
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.165: Got instructions of length 16
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.165: Received command SET_KEEP_ALIVE 0
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.166: Keep alive toggled: 0
(process:17363): libfprint-virtual_device_connection-DEBUG: 04:23:49.168: Got a new connection!
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.170: Got instructions of length 19
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.171: Received command SET_ENROLL_STAGES 5
(process:17363): libfprint-device-DEBUG: 04:23:49.173: Device reported close completion
(process:17363): libfprint-device-DEBUG: 04:23:49.174: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17363): libfprint-device-DEBUG: 04:23:49.174: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17363): libfprint-virtual_device-DEBUG: 04:23:49.179: 38977928776975: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.193s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:593: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 21/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_verify_no_match
start time: 04:23:48
duration: 0.72s
result: exit status 0
command: MALLOC_PERTURB_=190 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_enroll_verify_no_match
----------------------------------- stdout -----------------------------------
(process:17365): libfprint-context-DEBUG: 04:23:48.988: Initializing FpContext (libfprint version 1.94.6)
(process:17365): libfprint-context-DEBUG: 04:23:49.022: No driver found for USB device 1D6B:0003
(process:17365): libfprint-context-DEBUG: 04:23:49.023: No driver found for USB device 0BDA:5401
(process:17365): libfprint-context-DEBUG: 04:23:49.024: No driver found for USB device 1D6B:0002
(process:17365): libfprint-context-DEBUG: 04:23:49.024: No driver found for USB device 1D6B:0003
(process:17365): libfprint-context-DEBUG: 04:23:49.025: No driver found for USB device 0624:0249
(process:17365): libfprint-context-DEBUG: 04:23:49.025: No driver found for USB device 0624:0248
(process:17365): libfprint-context-DEBUG: 04:23:49.025: No driver found for USB device 1D6B:0002
(process:17365): libfprint-context-DEBUG: 04:23:49.026: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-4vxck5w8/virtual-device.socket
(process:17365): libfprint-context-DEBUG: 04:23:49.028: created
(process:17365): libfprint-device-DEBUG: 04:23:49.052: Device reported probe completion
(process:17365): libfprint-device-DEBUG: 04:23:49.053: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17365): libfprint-device-DEBUG: 04:23:49.054: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:17365): libfprint-virtual_device-DEBUG: 04:23:49.057: 38977928655550: ../libfprint/drivers/virtual-device.c:387
(process:17365): libfprint-virtual_device_connection-DEBUG: 04:23:49.068: 38977928666267: ../libfprint/drivers/virtual-device-listener.c:153
(process:17365): libfprint-device-DEBUG: 04:23:49.072: Device reported open completion
(process:17365): libfprint-device-DEBUG: 04:23:49.073: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17365): libfprint-device-DEBUG: 04:23:49.073: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17365): libfprint-virtual_device_connection-DEBUG: 04:23:49.087: Got a new connection!
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.089: Got instructions of length 14
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.089: Received command SCAN testprint
(process:17365): libfprint-device-DEBUG: 04:23:49.103: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.104: Processing command SCAN testprint
(process:17365): libfprint-device-DEBUG: 04:23:49.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17365): libfprint-device-DEBUG: 04:23:49.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17365): libfprint-device-DEBUG: 04:23:49.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17365): libfprint-device-DEBUG: 04:23:49.104: Device reported enroll progress, reported 1 of 5 have been completed
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.105: Sleeping completed
(process:17365): libfprint-virtual_device_connection-DEBUG: 04:23:49.115: Got a new connection!
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.116: Got instructions of length 14
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.116: Received command SCAN testprint
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.116: Processing command SCAN testprint
(process:17365): libfprint-device-DEBUG: 04:23:49.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17365): libfprint-device-DEBUG: 04:23:49.117: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17365): libfprint-device-DEBUG: 04:23:49.117: Device reported enroll progress, reported 2 of 5 have been completed
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.118: Sleeping completed
(process:17365): libfprint-virtual_device_connection-DEBUG: 04:23:49.127: Got a new connection!
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.129: Got instructions of length 14
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.129: Received command SCAN testprint
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.129: Processing command SCAN testprint
(process:17365): libfprint-device-DEBUG: 04:23:49.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17365): libfprint-device-DEBUG: 04:23:49.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17365): libfprint-device-DEBUG: 04:23:49.129: Device reported enroll progress, reported 3 of 5 have been completed
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.130: Sleeping completed
(process:17365): libfprint-virtual_device_connection-DEBUG: 04:23:49.132: Got a new connection!
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.133: Got instructions of length 14
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.133: Received command SCAN testprint
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.133: Processing command SCAN testprint
(process:17365): libfprint-device-DEBUG: 04:23:49.133: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17365): libfprint-device-DEBUG: 04:23:49.134: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17365): libfprint-device-DEBUG: 04:23:49.142: Device reported enroll progress, reported 4 of 5 have been completed
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.143: Sleeping completed
(process:17365): libfprint-virtual_device_connection-DEBUG: 04:23:49.145: Got a new connection!
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.146: Got instructions of length 14
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.146: Received command SCAN testprint
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.146: Processing command SCAN testprint
(process:17365): libfprint-device-DEBUG: 04:23:49.146: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17365): libfprint-device-DEBUG: 04:23:49.146: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17365): libfprint-device-DEBUG: 04:23:49.147: Device reported enroll progress, reported 5 of 5 have been completed
(process:17365): libfprint-device-DEBUG: 04:23:49.147: Device reported enroll completion
(process:17365): libfprint-device-DEBUG: 04:23:49.147: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17365): libfprint-device-DEBUG: 04:23:49.147: Print for finger FP_FINGER_LEFT_RING enrolled
(process:17365): libfprint-device-DEBUG: 04:23:49.148: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17365): libfprint-device-DEBUG: 04:23:49.148: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17365): libfprint-virtual_device_connection-DEBUG: 04:23:49.168: Got a new connection!
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.169: Got instructions of length 18
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.170: Received command SCAN not-testprint
(process:17365): libfprint-device-DEBUG: 04:23:49.176: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.177: Processing command SCAN not-testprint
(process:17365): libfprint-device-DEBUG: 04:23:49.177: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17365): libfprint-device-DEBUG: 04:23:49.177: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.177: Virtual device scanned print not-testprint
(process:17365): libfprint-device-DEBUG: 04:23:49.178: Device reported verify result
(process:17365): libfprint-device-DEBUG: 04:23:49.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17365): libfprint-device-DEBUG: 04:23:49.182: Device reported verify completion
(process:17365): libfprint-device-DEBUG: 04:23:49.182: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17365): libfprint-device-DEBUG: 04:23:49.182: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17365): libfprint-device-DEBUG: 04:23:49.183: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17365): libfprint-virtual_device_connection-DEBUG: 04:23:49.186: Got a new connection!
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.195: Got instructions of length 16
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.195: Received command SET_KEEP_ALIVE 0
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.195: Keep alive toggled: 0
(process:17365): libfprint-virtual_device_connection-DEBUG: 04:23:49.197: Got a new connection!
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.198: Got instructions of length 19
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.198: Received command SET_ENROLL_STAGES 5
(process:17365): libfprint-device-DEBUG: 04:23:49.200: Device reported close completion
(process:17365): libfprint-device-DEBUG: 04:23:49.200: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17365): libfprint-device-DEBUG: 04:23:49.201: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17365): libfprint-virtual_device-DEBUG: 04:23:49.211: 38977928809394: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.248s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:599: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 22/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_verify_error
start time: 04:23:48
duration: 0.92s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=28 FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_enroll_verify_error
----------------------------------- stdout -----------------------------------
(process:17361): libfprint-context-DEBUG: 04:23:49.035: Initializing FpContext (libfprint version 1.94.6)
(process:17361): libfprint-context-DEBUG: 04:23:49.091: No driver found for USB device 1D6B:0003
(process:17361): libfprint-context-DEBUG: 04:23:49.091: No driver found for USB device 0BDA:5401
(process:17361): libfprint-context-DEBUG: 04:23:49.091: No driver found for USB device 1D6B:0002
(process:17361): libfprint-context-DEBUG: 04:23:49.092: No driver found for USB device 1D6B:0003
(process:17361): libfprint-context-DEBUG: 04:23:49.092: No driver found for USB device 0624:0249
(process:17361): libfprint-context-DEBUG: 04:23:49.092: No driver found for USB device 0624:0248
(process:17361): libfprint-context-DEBUG: 04:23:49.092: No driver found for USB device 1D6B:0002
(process:17361): libfprint-context-DEBUG: 04:23:49.092: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-7qs4rgac/virtual-device.socket
(process:17361): libfprint-context-DEBUG: 04:23:49.094: created
(process:17361): libfprint-device-DEBUG: 04:23:49.114: Device reported probe completion
(process:17361): libfprint-device-DEBUG: 04:23:49.118: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17361): libfprint-device-DEBUG: 04:23:49.118: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:17361): libfprint-virtual_device-DEBUG: 04:23:49.121: 38977928719707: ../libfprint/drivers/virtual-device.c:387
(process:17361): libfprint-virtual_device_connection-DEBUG: 04:23:49.123: 38977928721117: ../libfprint/drivers/virtual-device-listener.c:153
(process:17361): libfprint-device-DEBUG: 04:23:49.126: Device reported open completion
(process:17361): libfprint-device-DEBUG: 04:23:49.126: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17361): libfprint-device-DEBUG: 04:23:49.126: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17361): libfprint-virtual_device_connection-DEBUG: 04:23:49.135: Got a new connection!
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.137: Got instructions of length 14
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.137: Received command SCAN testprint
(process:17361): libfprint-device-DEBUG: 04:23:49.151: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.151: Processing command SCAN testprint
(process:17361): libfprint-device-DEBUG: 04:23:49.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17361): libfprint-device-DEBUG: 04:23:49.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17361): libfprint-device-DEBUG: 04:23:49.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17361): libfprint-device-DEBUG: 04:23:49.152: Device reported enroll progress, reported 1 of 5 have been completed
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.153: Sleeping completed
(process:17361): libfprint-virtual_device_connection-DEBUG: 04:23:49.154: Got a new connection!
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.156: Got instructions of length 14
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.156: Received command SCAN testprint
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.156: Processing command SCAN testprint
(process:17361): libfprint-device-DEBUG: 04:23:49.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17361): libfprint-device-DEBUG: 04:23:49.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17361): libfprint-device-DEBUG: 04:23:49.156: Device reported enroll progress, reported 2 of 5 have been completed
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.157: Sleeping completed
(process:17361): libfprint-virtual_device_connection-DEBUG: 04:23:49.163: Got a new connection!
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.165: Got instructions of length 14
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.166: Received command SCAN testprint
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.166: Processing command SCAN testprint
(process:17361): libfprint-device-DEBUG: 04:23:49.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17361): libfprint-device-DEBUG: 04:23:49.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17361): libfprint-device-DEBUG: 04:23:49.168: Device reported enroll progress, reported 3 of 5 have been completed
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.169: Sleeping completed
(process:17361): libfprint-virtual_device_connection-DEBUG: 04:23:49.179: Got a new connection!
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.180: Got instructions of length 14
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.181: Received command SCAN testprint
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.181: Processing command SCAN testprint
(process:17361): libfprint-device-DEBUG: 04:23:49.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17361): libfprint-device-DEBUG: 04:23:49.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17361): libfprint-device-DEBUG: 04:23:49.183: Device reported enroll progress, reported 4 of 5 have been completed
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.185: Sleeping completed
(process:17361): libfprint-virtual_device_connection-DEBUG: 04:23:49.187: Got a new connection!
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.189: Got instructions of length 14
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.189: Received command SCAN testprint
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.189: Processing command SCAN testprint
(process:17361): libfprint-device-DEBUG: 04:23:49.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17361): libfprint-device-DEBUG: 04:23:49.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17361): libfprint-device-DEBUG: 04:23:49.191: Device reported enroll progress, reported 5 of 5 have been completed
(process:17361): libfprint-device-DEBUG: 04:23:49.192: Device reported enroll completion
(process:17361): libfprint-device-DEBUG: 04:23:49.192: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17361): libfprint-device-DEBUG: 04:23:49.193: Print for finger FP_FINGER_LEFT_RING enrolled
(process:17361): libfprint-device-DEBUG: 04:23:49.203: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17361): libfprint-device-DEBUG: 04:23:49.204: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17361): libfprint-virtual_device_connection-DEBUG: 04:23:49.219: Got a new connection!
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.220: Got instructions of length 7
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.221: Received command ERROR 0
(process:17361): libfprint-device-DEBUG: 04:23:49.224: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.225: Processing command ERROR 0
(process:17361): libfprint-device-DEBUG: 04:23:49.225: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.226: Virtual device scan failed with error: An unspecified error occurred!
(process:17361): libfprint-device-DEBUG: 04:23:49.230: Device reported verify completion
(process:17361): libfprint-device-DEBUG: 04:23:49.231: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17361): libfprint-device-DEBUG: 04:23:49.232: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17361): libfprint-device-DEBUG: 04:23:49.232: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17361): libfprint-virtual_device_connection-DEBUG: 04:23:49.235: Got a new connection!
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.237: Got instructions of length 16
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.237: Received command SET_KEEP_ALIVE 0
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.238: Keep alive toggled: 0
(process:17361): libfprint-virtual_device_connection-DEBUG: 04:23:49.244: Got a new connection!
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.246: Got instructions of length 19
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.246: Received command SET_ENROLL_STAGES 5
(process:17361): libfprint-device-DEBUG: 04:23:49.248: Device reported close completion
(process:17361): libfprint-device-DEBUG: 04:23:49.249: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17361): libfprint-device-DEBUG: 04:23:49.250: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17361): libfprint-virtual_device-DEBUG: 04:23:49.257: 38977928855049: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.244s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:606: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 23/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_verify_retry
start time: 04:23:49
duration: 0.89s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests MALLOC_PERTURB_=141 FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_enroll_verify_retry
----------------------------------- stdout -----------------------------------
(process:17376): libfprint-context-DEBUG: 04:23:49.952: Initializing FpContext (libfprint version 1.94.6)
(process:17376): libfprint-context-DEBUG: 04:23:49.997: No driver found for USB device 1D6B:0003
(process:17376): libfprint-context-DEBUG: 04:23:49.997: No driver found for USB device 0BDA:5401
(process:17376): libfprint-context-DEBUG: 04:23:49.997: No driver found for USB device 1D6B:0002
(process:17376): libfprint-context-DEBUG: 04:23:49.997: No driver found for USB device 1D6B:0003
(process:17376): libfprint-context-DEBUG: 04:23:49.998: No driver found for USB device 0624:0249
(process:17376): libfprint-context-DEBUG: 04:23:49.998: No driver found for USB device 0624:0248
(process:17376): libfprint-context-DEBUG: 04:23:49.998: No driver found for USB device 1D6B:0002
(process:17376): libfprint-context-DEBUG: 04:23:49.998: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-mil_94pf/virtual-device.socket
(process:17376): libfprint-context-DEBUG: 04:23:50.000: created
(process:17376): libfprint-device-DEBUG: 04:23:50.023: Device reported probe completion
(process:17376): libfprint-device-DEBUG: 04:23:50.023: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17376): libfprint-device-DEBUG: 04:23:50.024: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:17376): libfprint-virtual_device-DEBUG: 04:23:50.026: 38977929624716: ../libfprint/drivers/virtual-device.c:387
(process:17376): libfprint-virtual_device_connection-DEBUG: 04:23:50.029: 38977929626959: ../libfprint/drivers/virtual-device-listener.c:153
(process:17376): libfprint-device-DEBUG: 04:23:50.037: Device reported open completion
(process:17376): libfprint-device-DEBUG: 04:23:50.037: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17376): libfprint-device-DEBUG: 04:23:50.037: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17376): libfprint-virtual_device_connection-DEBUG: 04:23:50.052: Got a new connection!
(process:17376): libfprint-virtual_device-DEBUG: 04:23:50.054: Got instructions of length 7
(process:17376): libfprint-virtual_device-DEBUG: 04:23:50.054: Received command RETRY 1
(process:17376): libfprint-device-DEBUG: 04:23:50.057: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17376): libfprint-virtual_device-DEBUG: 04:23:50.058: Processing command RETRY 1
(process:17376): libfprint-device-DEBUG: 04:23:50.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17376): libfprint-virtual_device-DEBUG: 04:23:50.066: Virtual device scan failed with error: The swipe was too short, please try again.
(process:17376): libfprint-device-DEBUG: 04:23:50.066: Device reported verify result
(process:17376): libfprint-device-DEBUG: 04:23:50.066: Device reported verify completion
(process:17376): libfprint-device-DEBUG: 04:23:50.067: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17376): libfprint-device-DEBUG: 04:23:50.067: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17376): libfprint-device-DEBUG: 04:23:50.067: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17376): libfprint-virtual_device_connection-DEBUG: 04:23:50.071: Got a new connection!
(process:17376): libfprint-virtual_device-DEBUG: 04:23:50.072: Got instructions of length 16
(process:17376): libfprint-virtual_device-DEBUG: 04:23:50.072: Received command SET_KEEP_ALIVE 0
(process:17376): libfprint-virtual_device-DEBUG: 04:23:50.072: Keep alive toggled: 0
(process:17376): libfprint-virtual_device_connection-DEBUG: 04:23:50.082: Got a new connection!
(process:17376): libfprint-virtual_device-DEBUG: 04:23:50.083: Got instructions of length 19
(process:17376): libfprint-virtual_device-DEBUG: 04:23:50.083: Received command SET_ENROLL_STAGES 5
(process:17376): libfprint-device-DEBUG: 04:23:50.085: Device reported close completion
(process:17376): libfprint-device-DEBUG: 04:23:50.085: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17376): libfprint-device-DEBUG: 04:23:50.086: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
(process:17376): libfprint-virtual_device-DEBUG: 04:23:50.088: 38977929686045: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.158s
OK
==============================================================================
=================================== 24/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_with_retry
start time: 04:23:49
duration: 0.90s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=221 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_enroll_with_retry
----------------------------------- stdout -----------------------------------
(process:17380): libfprint-context-DEBUG: 04:23:49.981: Initializing FpContext (libfprint version 1.94.6)
(process:17380): libfprint-context-DEBUG: 04:23:50.033: No driver found for USB device 1D6B:0003
(process:17380): libfprint-context-DEBUG: 04:23:50.033: No driver found for USB device 0BDA:5401
(process:17380): libfprint-context-DEBUG: 04:23:50.033: No driver found for USB device 1D6B:0002
(process:17380): libfprint-context-DEBUG: 04:23:50.033: No driver found for USB device 1D6B:0003
(process:17380): libfprint-context-DEBUG: 04:23:50.033: No driver found for USB device 0624:0249
(process:17380): libfprint-context-DEBUG: 04:23:50.034: No driver found for USB device 0624:0248
(process:17380): libfprint-context-DEBUG: 04:23:50.042: No driver found for USB device 1D6B:0002
(process:17380): libfprint-context-DEBUG: 04:23:50.042: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-amalybav/virtual-device.socket
(process:17380): libfprint-context-DEBUG: 04:23:50.043: created
(process:17380): libfprint-device-DEBUG: 04:23:50.064: Device reported probe completion
(process:17380): libfprint-device-DEBUG: 04:23:50.064: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17380): libfprint-device-DEBUG: 04:23:50.064: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:17380): libfprint-virtual_device-DEBUG: 04:23:50.071: 38977929669737: ../libfprint/drivers/virtual-device.c:387
(process:17380): libfprint-virtual_device_connection-DEBUG: 04:23:50.073: 38977929671117: ../libfprint/drivers/virtual-device-listener.c:153
(process:17380): libfprint-device-DEBUG: 04:23:50.080: Device reported open completion
(process:17380): libfprint-device-DEBUG: 04:23:50.081: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17380): libfprint-device-DEBUG: 04:23:50.081: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17380): libfprint-virtual_device_connection-DEBUG: 04:23:50.089: Got a new connection!
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.095: Got instructions of length 14
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.096: Received command SCAN testprint
(process:17380): libfprint-device-DEBUG: 04:23:50.108: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.108: Processing command SCAN testprint
(process:17380): libfprint-device-DEBUG: 04:23:50.108: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17380): libfprint-device-DEBUG: 04:23:50.108: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17380): libfprint-device-DEBUG: 04:23:50.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17380): libfprint-device-DEBUG: 04:23:50.109: Device reported enroll progress, reported 1 of 5 have been completed
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.110: Sleeping completed
(process:17380): libfprint-virtual_device_connection-DEBUG: 04:23:50.111: Got a new connection!
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.112: Got instructions of length 14
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.112: Received command SCAN testprint
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.112: Processing command SCAN testprint
(process:17380): libfprint-device-DEBUG: 04:23:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17380): libfprint-device-DEBUG: 04:23:50.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17380): libfprint-device-DEBUG: 04:23:50.113: Device reported enroll progress, reported 2 of 5 have been completed
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.114: Sleeping completed
(process:17380): libfprint-virtual_device_connection-DEBUG: 04:23:50.117: Got a new connection!
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.122: Got instructions of length 7
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.123: Received command RETRY 1
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.123: Processing command RETRY 1
(process:17380): libfprint-device-DEBUG: 04:23:50.123: Device reported enroll progress, reported 2 of 5 have been completed
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.124: Sleeping completed
(process:17380): libfprint-virtual_device_connection-DEBUG: 04:23:50.126: Got a new connection!
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.127: Got instructions of length 14
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.127: Received command SCAN testprint
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.127: Processing command SCAN testprint
(process:17380): libfprint-device-DEBUG: 04:23:50.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17380): libfprint-device-DEBUG: 04:23:50.128: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17380): libfprint-device-DEBUG: 04:23:50.128: Device reported enroll progress, reported 3 of 5 have been completed
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.129: Sleeping completed
(process:17380): libfprint-virtual_device_connection-DEBUG: 04:23:50.135: Got a new connection!
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.136: Got instructions of length 14
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.136: Received command SCAN testprint
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.136: Processing command SCAN testprint
(process:17380): libfprint-device-DEBUG: 04:23:50.136: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17380): libfprint-device-DEBUG: 04:23:50.136: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17380): libfprint-device-DEBUG: 04:23:50.136: Device reported enroll progress, reported 4 of 5 have been completed
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.137: Sleeping completed
(process:17380): libfprint-virtual_device_connection-DEBUG: 04:23:50.139: Got a new connection!
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.140: Got instructions of length 14
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.140: Received command SCAN testprint
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.141: Processing command SCAN testprint
(process:17380): libfprint-device-DEBUG: 04:23:50.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17380): libfprint-device-DEBUG: 04:23:50.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17380): libfprint-device-DEBUG: 04:23:50.141: Device reported enroll progress, reported 5 of 5 have been completed
(process:17380): libfprint-device-DEBUG: 04:23:50.141: Device reported enroll completion
(process:17380): libfprint-device-DEBUG: 04:23:50.141: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17380): libfprint-device-DEBUG: 04:23:50.142: Print for finger FP_FINGER_LEFT_LITTLE enrolled
(process:17380): libfprint-device-DEBUG: 04:23:50.151: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17380): libfprint-device-DEBUG: 04:23:50.151: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17380): libfprint-virtual_device_connection-DEBUG: 04:23:50.159: Got a new connection!
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.160: Got instructions of length 16
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.160: Received command SET_KEEP_ALIVE 0
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.160: Keep alive toggled: 0
(process:17380): libfprint-virtual_device_connection-DEBUG: 04:23:50.162: Got a new connection!
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.163: Got instructions of length 19
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.163: Received command SET_ENROLL_STAGES 5
(process:17380): libfprint-device-DEBUG: 04:23:50.165: Device reported close completion
(process:17380): libfprint-device-DEBUG: 04:23:50.165: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17380): libfprint-device-DEBUG: 04:23:50.165: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17380): libfprint-virtual_device-DEBUG: 04:23:50.167: 38977929765539: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.210s
OK
==============================================================================
=================================== 25/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_enroll_verify_script
start time: 04:23:49
duration: 1.03s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=182 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_enroll_verify_script
----------------------------------- stdout -----------------------------------
(process:17378): libfprint-context-DEBUG: 04:23:49.932: Initializing FpContext (libfprint version 1.94.6)
(process:17378): libfprint-context-DEBUG: 04:23:49.962: No driver found for USB device 1D6B:0003
(process:17378): libfprint-context-DEBUG: 04:23:49.963: No driver found for USB device 0BDA:5401
(process:17378): libfprint-context-DEBUG: 04:23:49.963: No driver found for USB device 1D6B:0002
(process:17378): libfprint-context-DEBUG: 04:23:49.963: No driver found for USB device 1D6B:0003
(process:17378): libfprint-context-DEBUG: 04:23:49.963: No driver found for USB device 0624:0249
(process:17378): libfprint-context-DEBUG: 04:23:49.963: No driver found for USB device 0624:0248
(process:17378): libfprint-context-DEBUG: 04:23:49.963: No driver found for USB device 1D6B:0002
(process:17378): libfprint-context-DEBUG: 04:23:49.964: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-2iby9og6/virtual-device.socket
(process:17378): libfprint-context-DEBUG: 04:23:49.965: created
(process:17378): libfprint-device-DEBUG: 04:23:49.976: Device reported probe completion
(process:17378): libfprint-device-DEBUG: 04:23:49.977: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17378): libfprint-device-DEBUG: 04:23:49.977: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:17378): libfprint-virtual_device-DEBUG: 04:23:49.980: 38977929578456: ../libfprint/drivers/virtual-device.c:387
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:49.982: 38977929579761: ../libfprint/drivers/virtual-device-listener.c:153
(process:17378): libfprint-device-DEBUG: 04:23:49.985: Device reported open completion
(process:17378): libfprint-device-DEBUG: 04:23:49.985: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17378): libfprint-device-DEBUG: 04:23:49.985: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:49.988: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:49.990: Got instructions of length 19
(process:17378): libfprint-virtual_device-DEBUG: 04:23:49.990: Received command SET_ENROLL_STAGES 8
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:49.993: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:49.995: Got instructions of length 13
(process:17378): libfprint-virtual_device-DEBUG: 04:23:49.995: Received command SCAN print-id
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:49.999: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.001: Got instructions of length 13
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.001: Received command SCAN print-id
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.005: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.007: Got instructions of length 7
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.007: Received command RETRY 1
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.009: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.011: Got instructions of length 13
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.012: Received command SCAN print-id
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.014: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.015: Got instructions of length 7
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.016: Received command RETRY 3
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.018: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.020: Got instructions of length 13
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.020: Received command SCAN print-id
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.022: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.024: Got instructions of length 7
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.025: Received command RETRY 2
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.027: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.028: Got instructions of length 13
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.028: Received command SCAN print-id
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.030: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.031: Got instructions of length 8
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.032: Received command SLEEP 10
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.034: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.035: Got instructions of length 8
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.035: Received command SLEEP 20
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.038: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.039: Got instructions of length 7
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.040: Received command RETRY 0
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.042: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.044: Got instructions of length 7
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.045: Received command RETRY 3
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.047: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.051: Got instructions of length 13
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.052: Received command SCAN print-id
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.054: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.056: Got instructions of length 15
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.056: Received command SCAN another-id
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.059: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.060: Got instructions of length 13
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.061: Received command SCAN print-id
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.063: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.065: Got instructions of length 13
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.066: Received command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.073: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.074: Processing command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17378): libfprint-device-DEBUG: 04:23:50.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.076: Device reported enroll progress, reported 1 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.076: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.077: Processing command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.077: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17378): libfprint-device-DEBUG: 04:23:50.078: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.078: Device reported enroll progress, reported 2 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.079: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.079: Processing command RETRY 1
(process:17378): libfprint-device-DEBUG: 04:23:50.080: Device reported enroll progress, reported 2 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.080: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.081: Processing command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17378): libfprint-device-DEBUG: 04:23:50.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.083: Device reported enroll progress, reported 3 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.083: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.084: Processing command RETRY 3
(process:17378): libfprint-device-DEBUG: 04:23:50.084: Device reported enroll progress, reported 3 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.085: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.085: Processing command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.086: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17378): libfprint-device-DEBUG: 04:23:50.087: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.087: Device reported enroll progress, reported 4 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.088: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.088: Processing command RETRY 2
(process:17378): libfprint-device-DEBUG: 04:23:50.089: Device reported enroll progress, reported 4 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.089: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.090: Processing command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.090: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17378): libfprint-device-DEBUG: 04:23:50.091: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.092: Device reported enroll progress, reported 5 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.092: Processing command SLEEP 10
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.092: Sleeping 10ms
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.106: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.106: Processing command SLEEP 20
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.106: Sleeping 20ms
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.130: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.130: Processing command RETRY 0
(process:17378): libfprint-device-DEBUG: 04:23:50.130: Device reported enroll progress, reported 5 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.130: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.130: Processing command RETRY 3
(process:17378): libfprint-device-DEBUG: 04:23:50.131: Device reported enroll progress, reported 5 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.131: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.131: Processing command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.131: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17378): libfprint-device-DEBUG: 04:23:50.131: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.131: Device reported enroll progress, reported 6 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.132: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.132: Processing command SCAN another-id
(process:17378): libfprint-device-DEBUG: 04:23:50.132: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17378): libfprint-device-DEBUG: 04:23:50.132: Device reported enroll progress, reported 6 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.132: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.133: Processing command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.133: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.133: Device reported enroll progress, reported 7 of 8 have been completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.133: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.133: Processing command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.133: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17378): libfprint-device-DEBUG: 04:23:50.134: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.134: Device reported enroll progress, reported 8 of 8 have been completed
(process:17378): libfprint-device-DEBUG: 04:23:50.134: Device reported enroll completion
(process:17378): libfprint-device-DEBUG: 04:23:50.134: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17378): libfprint-device-DEBUG: 04:23:50.134: Print for finger FP_FINGER_UNKNOWN enrolled
(process:17378): libfprint-device-DEBUG: 04:23:50.135: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17378): libfprint-device-DEBUG: 04:23:50.135: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.138: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.139: Got instructions of length 7
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.139: Received command RETRY 2
(process:17378): libfprint-device-DEBUG: 04:23:50.141: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.146: Processing command RETRY 2
(process:17378): libfprint-device-DEBUG: 04:23:50.146: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.146: Virtual device scan failed with error: The finger was not centered properly, please try again.
(process:17378): libfprint-device-DEBUG: 04:23:50.146: Device reported verify result
(process:17378): libfprint-device-DEBUG: 04:23:50.147: Device reported verify completion
(process:17378): libfprint-device-DEBUG: 04:23:50.147: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17378): libfprint-device-DEBUG: 04:23:50.147: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17378): libfprint-device-DEBUG: 04:23:50.147: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.149: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.154: Got instructions of length 8
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.155: Received command SLEEP 50
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.157: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.158: Got instructions of length 7
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.162: Received command RETRY 1
(process:17378): libfprint-device-DEBUG: 04:23:50.163: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.163: Processing command SLEEP 50
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.163: Sleeping 50ms
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.218: Sleeping completed
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.218: Processing command RETRY 1
(process:17378): libfprint-device-DEBUG: 04:23:50.218: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.218: Virtual device scan failed with error: The swipe was too short, please try again.
(process:17378): libfprint-device-DEBUG: 04:23:50.218: Device reported verify result
(process:17378): libfprint-device-DEBUG: 04:23:50.218: Device reported verify completion
(process:17378): libfprint-device-DEBUG: 04:23:50.219: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17378): libfprint-device-DEBUG: 04:23:50.219: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17378): libfprint-device-DEBUG: 04:23:50.219: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.221: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.222: Got instructions of length 15
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.222: Received command SCAN another-id
(process:17378): libfprint-device-DEBUG: 04:23:50.223: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.223: Processing command SCAN another-id
(process:17378): libfprint-device-DEBUG: 04:23:50.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.224: Virtual device scanned print another-id
(process:17378): libfprint-device-DEBUG: 04:23:50.224: Device reported verify result
(process:17378): libfprint-device-DEBUG: 04:23:50.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.224: Device reported verify completion
(process:17378): libfprint-device-DEBUG: 04:23:50.225: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17378): libfprint-device-DEBUG: 04:23:50.225: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17378): libfprint-device-DEBUG: 04:23:50.225: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.230: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.231: Got instructions of length 13
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.231: Received command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.232: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.232: Processing command SCAN print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.232: Virtual device scanned print print-id
(process:17378): libfprint-device-DEBUG: 04:23:50.233: Device reported verify result
(process:17378): libfprint-device-DEBUG: 04:23:50.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17378): libfprint-device-DEBUG: 04:23:50.233: Device reported verify completion
(process:17378): libfprint-device-DEBUG: 04:23:50.233: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17378): libfprint-device-DEBUG: 04:23:50.233: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17378): libfprint-device-DEBUG: 04:23:50.238: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.240: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.241: Got instructions of length 16
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.241: Received command SET_KEEP_ALIVE 0
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.241: Keep alive toggled: 0
(process:17378): libfprint-virtual_device_connection-DEBUG: 04:23:50.243: Got a new connection!
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.244: Got instructions of length 19
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.244: Received command SET_ENROLL_STAGES 5
(process:17378): libfprint-device-DEBUG: 04:23:50.246: Device reported close completion
(process:17378): libfprint-device-DEBUG: 04:23:50.247: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17378): libfprint-device-DEBUG: 04:23:50.247: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
(process:17378): libfprint-virtual_device-DEBUG: 04:23:50.249: 38977929846995: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.335s
OK
==============================================================================
=================================== 26/116 ===================================
test: libfprint:virtual-driver+virtual-image+VirtualImage / VirtualImage.test_enroll_verify
start time: 04:23:37
duration: 13.65s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all MALLOC_PERTURB_=226 G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-image.py VirtualImage.test_enroll_verify
----------------------------------- stdout -----------------------------------
(process:17257): libfprint-context-DEBUG: 04:23:37.809: Initializing FpContext (libfprint version 1.94.6)
(process:17257): libfprint-context-DEBUG: 04:23:37.885: No driver found for USB device 1D6B:0003
(process:17257): libfprint-context-DEBUG: 04:23:37.885: No driver found for USB device 0BDA:5401
(process:17257): libfprint-context-DEBUG: 04:23:37.885: No driver found for USB device 1D6B:0002
(process:17257): libfprint-context-DEBUG: 04:23:37.886: No driver found for USB device 1D6B:0003
(process:17257): libfprint-context-DEBUG: 04:23:37.886: No driver found for USB device 0624:0249
(process:17257): libfprint-context-DEBUG: 04:23:37.886: No driver found for USB device 0624:0248
(process:17257): libfprint-context-DEBUG: 04:23:37.886: No driver found for USB device 1D6B:0002
(process:17257): libfprint-context-DEBUG: 04:23:37.886: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-fg2wtkog/virtual-image.socket
(process:17257): libfprint-context-DEBUG: 04:23:37.888: created
(process:17257): libfprint-device-DEBUG: 04:23:37.916: Device reported probe completion
(process:17257): libfprint-device-DEBUG: 04:23:37.917: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17257): libfprint-device-DEBUG: 04:23:37.917: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:17257): libfprint-virtual_image-DEBUG: 04:23:37.977: 38977917575471: ../libfprint/drivers/virtual-image.c:216
(process:17257): libfprint-virtual_device_connection-DEBUG: 04:23:37.983: 38977917580943: ../libfprint/drivers/virtual-device-listener.c:153
(process:17257): libfprint-image_device-DEBUG: 04:23:38.090: Image device open completed
(process:17257): libfprint-device-DEBUG: 04:23:38.090: Device reported open completion
(process:17257): libfprint-device-DEBUG: 04:23:38.090: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17257): libfprint-device-DEBUG: 04:23:38.091: Updated temperature model after 0.17 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17257): libfprint-device-DEBUG: 04:23:38.120: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17257): libfprint-image_device-DEBUG: 04:23:38.120: Activating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:38.120: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:38.121: Image device activation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:38.121: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.121: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:38.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_device_connection-DEBUG: 04:23:38.123: Got a new connection!
(process:17257): libfprint-virtual_image-DEBUG: 04:23:38.126: image data: 0x1c1e608
(process:17257): libfprint-device-DEBUG: 04:23:38.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:38.127: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:38.128: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.128: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:38.128: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:38.128: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:38.129: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.129: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:38.129: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-device-DEBUG: 04:23:38.222: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17257): libfprint-image-DEBUG: 04:23:38.296: Minutiae scan completed in 0.166350 secs
(process:17257): libfprint-device-DEBUG: 04:23:38.298: Device reported enroll progress, reported 1 of 5 have been completed
(process:17257): libfprint-image_device-DEBUG: 04:23:38.299: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:38.299: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-device-DEBUG: 04:23:38.302: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:38.302: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:38.302: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-virtual_image-DEBUG: 04:23:38.305: image data: 0x1c1e608
(process:17257): libfprint-image_device-DEBUG: 04:23:38.314: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:38.315: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:38.315: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image-DEBUG: 04:23:38.480: Minutiae scan completed in 0.161748 secs
(process:17257): libfprint-device-DEBUG: 04:23:38.480: Device reported enroll progress, reported 2 of 5 have been completed
(process:17257): libfprint-device-DEBUG: 04:23:38.482: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.482: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:38.482: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.482: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:38.483: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:38.487: image data: 0x1c1e608
(process:17257): libfprint-device-DEBUG: 04:23:38.488: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:38.488: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:38.488: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.489: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:38.489: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:38.489: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:38.489: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.489: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:38.489: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image-DEBUG: 04:23:38.644: Minutiae scan completed in 0.153985 secs
(process:17257): libfprint-device-DEBUG: 04:23:38.645: Device reported enroll progress, reported 3 of 5 have been completed
(process:17257): libfprint-image_device-DEBUG: 04:23:38.646: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:38.646: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:38.648: image data: 0x1c1e608
(process:17257): libfprint-device-DEBUG: 04:23:38.654: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:38.655: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:38.655: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.656: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:38.670: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:38.671: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:38.671: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.671: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:38.672: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image-DEBUG: 04:23:38.816: Minutiae scan completed in 0.158960 secs
(process:17257): libfprint-device-DEBUG: 04:23:38.816: Device reported enroll progress, reported 4 of 5 have been completed
(process:17257): libfprint-image_device-DEBUG: 04:23:38.817: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:38.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:38.818: image data: 0x1c1e608
(process:17257): libfprint-device-DEBUG: 04:23:38.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:38.820: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:38.820: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.820: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:38.821: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:38.821: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:38.821: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:38.821: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:38.821: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image-DEBUG: 04:23:38.994: Minutiae scan completed in 0.170577 secs
(process:17257): libfprint-device-DEBUG: 04:23:38.995: Device reported enroll progress, reported 5 of 5 have been completed
(process:17257): libfprint-image_device-DEBUG: 04:23:38.996: Deactivating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:38.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:38.996: Image device deactivation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:38.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17257): libfprint-device-DEBUG: 04:23:38.996: Device reported enroll completion
(process:17257): libfprint-device-DEBUG: 04:23:38.996: Print for finger FP_FINGER_LEFT_THUMB enrolled
(process:17257): libfprint-device-DEBUG: 04:23:38.997: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17257): libfprint-device-DEBUG: 04:23:38.997: Updated temperature model after 0.78 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-device-DEBUG: 04:23:39.005: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-image_device-DEBUG: 04:23:39.005: Activating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:39.006: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:39.006: Image device activation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:39.006: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:39.006: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:39.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:39.008: image data: 0x1c1e608
(process:17257): libfprint-device-DEBUG: 04:23:39.019: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:39.020: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:39.020: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:39.021: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:39.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:39.029: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:39.030: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:39.030: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:39.030: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:39.030: Deactivating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:39.030: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:39.030: Image device deactivation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:39.030: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17257): libfprint-image-DEBUG: 04:23:39.192: Minutiae scan completed in 0.169726 secs
(process:17257): libfprint-print-DEBUG: 04:23:43.730: score 1093/40
(process:17257): libfprint-device-DEBUG: 04:23:43.731: Device reported verify result
(process:17257): libfprint-device-DEBUG: 04:23:43.731: Device reported verify completion
(process:17257): libfprint-device-DEBUG: 04:23:43.732: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17257): libfprint-device-DEBUG: 04:23:43.733: Updated temperature model after 4.73 seconds, ratio 0.27 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-device-DEBUG: 04:23:43.735: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-image_device-DEBUG: 04:23:43.736: Activating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:43.736: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:43.737: Image device activation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:43.737: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:43.738: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:43.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:43.739: image data: 0x1c1fd80
(process:17257): libfprint-device-DEBUG: 04:23:43.742: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:43.742: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:43.743: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:43.743: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:43.758: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:43.759: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:43.759: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:43.759: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:43.760: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:43.760: Deactivating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:43.761: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:43.761: Image device deactivation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:43.761: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17257): libfprint-image-DEBUG: 04:23:43.832: Minutiae scan completed in 0.088384 secs
(process:17257): libfprint-print-DEBUG: 04:23:43.857: score 10/40
(process:17257): libfprint-print-DEBUG: 04:23:43.895: score 10/40
(process:17257): libfprint-print-DEBUG: 04:23:43.951: score 10/40
(process:17257): libfprint-print-DEBUG: 04:23:44.004: score 10/40
(process:17257): libfprint-print-DEBUG: 04:23:44.042: score 10/40
(process:17257): libfprint-device-DEBUG: 04:23:44.043: Device reported verify result
(process:17257): libfprint-device-DEBUG: 04:23:44.043: Device reported verify completion
(process:17257): libfprint-device-DEBUG: 04:23:44.044: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17257): libfprint-device-DEBUG: 04:23:44.045: Updated temperature model after 0.31 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-device-DEBUG: 04:23:44.046: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-image_device-DEBUG: 04:23:44.047: Activating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:44.047: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:44.048: Image device activation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:44.048: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.049: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:44.049: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:44.050: image data: 0x1c1fd80
(process:17257): libfprint-device-DEBUG: 04:23:44.053: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:44.054: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:44.054: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.054: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:44.070: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:44.070: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:44.071: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.071: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:44.072: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image-DEBUG: 04:23:44.142: Minutiae scan completed in 0.086506 secs
(process:17257): libfprint-device-DEBUG: 04:23:44.143: Device reported enroll progress, reported 1 of 5 have been completed
(process:17257): libfprint-image_device-DEBUG: 04:23:44.143: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:44.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-device-DEBUG: 04:23:44.146: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:44.147: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:44.147: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-virtual_image-DEBUG: 04:23:44.149: image data: 0x1c4cd98
(process:17257): libfprint-image_device-DEBUG: 04:23:44.151: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:44.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:44.151: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image-DEBUG: 04:23:44.238: Minutiae scan completed in 0.084212 secs
(process:17257): libfprint-device-DEBUG: 04:23:44.239: Device reported enroll progress, reported 2 of 5 have been completed
(process:17257): libfprint-device-DEBUG: 04:23:44.240: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.240: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:44.240: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.241: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:44.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:44.245: image data: 0x1c12038
(process:17257): libfprint-device-DEBUG: 04:23:44.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:44.247: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:44.247: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.247: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:44.247: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:44.248: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:44.248: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.248: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:44.248: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image-DEBUG: 04:23:44.415: Minutiae scan completed in 0.167440 secs
(process:17257): libfprint-device-DEBUG: 04:23:44.426: Device reported enroll progress, reported 3 of 5 have been completed
(process:17257): libfprint-image_device-DEBUG: 04:23:44.427: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:44.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:44.429: image data: 0x1c3e6f8
(process:17257): libfprint-device-DEBUG: 04:23:44.430: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:44.430: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:44.430: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.431: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:44.431: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:44.431: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:44.431: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.431: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:44.432: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image-DEBUG: 04:23:44.542: Minutiae scan completed in 0.108856 secs
(process:17257): libfprint-device-DEBUG: 04:23:44.543: Device reported enroll progress, reported 4 of 5 have been completed
(process:17257): libfprint-image_device-DEBUG: 04:23:44.543: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:44.543: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:44.545: image data: 0x1c5c708
(process:17257): libfprint-device-DEBUG: 04:23:44.546: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:44.546: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:44.546: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.547: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:44.547: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:44.547: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:44.547: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.547: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:44.548: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image-DEBUG: 04:23:44.710: Minutiae scan completed in 0.162795 secs
(process:17257): libfprint-device-DEBUG: 04:23:44.711: Device reported enroll progress, reported 5 of 5 have been completed
(process:17257): libfprint-image_device-DEBUG: 04:23:44.711: Deactivating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:44.711: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:44.711: Image device deactivation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:44.711: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17257): libfprint-device-DEBUG: 04:23:44.711: Device reported enroll completion
(process:17257): libfprint-device-DEBUG: 04:23:44.711: Print for finger FP_FINGER_LEFT_THUMB enrolled
(process:17257): libfprint-device-DEBUG: 04:23:44.712: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17257): libfprint-device-DEBUG: 04:23:44.712: Updated temperature model after 0.67 seconds, ratio 0.29 -> 0.30, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-device-DEBUG: 04:23:44.714: Updated temperature model after 0.00 seconds, ratio 0.30 -> 0.30, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-image_device-DEBUG: 04:23:44.714: Activating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:44.714: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:44.715: Image device activation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:44.715: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.715: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:44.715: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:44.716: image data: 0x1c121f0
(process:17257): libfprint-device-DEBUG: 04:23:44.718: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:44.718: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:44.718: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.718: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:44.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:44.719: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:44.719: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.719: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:44.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:44.719: Deactivating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:44.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:44.719: Image device deactivation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:44.720: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17257): libfprint-image-DEBUG: 04:23:44.884: Minutiae scan completed in 0.162278 secs
(process:17257): libfprint-print-DEBUG: 04:23:48.796: score 1093/40
(process:17257): libfprint-device-DEBUG: 04:23:48.796: Device reported verify result
(process:17257): libfprint-device-DEBUG: 04:23:48.797: Device reported verify completion
(process:17257): libfprint-device-DEBUG: 04:23:48.797: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17257): libfprint-device-DEBUG: 04:23:48.798: Updated temperature model after 4.08 seconds, ratio 0.30 -> 0.31, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-device-DEBUG: 04:23:48.800: Updated temperature model after 0.00 seconds, ratio 0.31 -> 0.31, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-image_device-DEBUG: 04:23:48.800: Activating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:48.801: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:48.802: Image device activation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:48.802: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:48.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:48.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-virtual_image-DEBUG: 04:23:48.804: image data: 0x1c129a0
(process:17257): libfprint-device-DEBUG: 04:23:48.807: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-image_device-DEBUG: 04:23:48.808: Image device reported finger status: on
(process:17257): libfprint-image_device-DEBUG: 04:23:48.808: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17257): libfprint-image_device-DEBUG: 04:23:48.809: Image device captured an image
(process:17257): libfprint-image_device-DEBUG: 04:23:48.809: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17257): libfprint-device-DEBUG: 04:23:48.810: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17257): libfprint-device-DEBUG: 04:23:48.810: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-image_device-DEBUG: 04:23:48.811: Image device reported finger status: off
(process:17257): libfprint-image_device-DEBUG: 04:23:48.811: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:48.811: Deactivating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:48.812: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:48.813: Image device deactivation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:48.813: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17257): libfprint-image-DEBUG: 04:23:48.946: Minutiae scan completed in 0.135786 secs
(process:17257): libfprint-print-DEBUG: 04:23:49.000: score 10/40
(process:17257): libfprint-print-DEBUG: 04:23:49.049: score 10/40
(process:17257): libfprint-print-DEBUG: 04:23:49.094: score 10/40
(process:17257): libfprint-print-DEBUG: 04:23:49.132: score 10/40
(process:17257): libfprint-print-DEBUG: 04:23:49.169: score 10/40
(process:17257): libfprint-print-DEBUG: 04:23:50.438: score 855/40
(process:17257): libfprint-device-DEBUG: 04:23:50.438: Device reported verify result
(process:17257): libfprint-device-DEBUG: 04:23:50.446: Device reported verify completion
(process:17257): libfprint-device-DEBUG: 04:23:50.447: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17257): libfprint-device-DEBUG: 04:23:50.447: Updated temperature model after 1.65 seconds, ratio 0.31 -> 0.32, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-device-DEBUG: 04:23:50.448: Updated temperature model after 0.00 seconds, ratio 0.32 -> 0.32, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-image_device-DEBUG: 04:23:50.449: Activating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:50.449: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:50.449: Image device activation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:50.449: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:50.450: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:50.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-device-DEBUG: 04:23:50.451: Device reported verify result
(process:17257): libfprint-image_device-DEBUG: 04:23:50.451: Deactivating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:50.451: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:50.452: Image device deactivation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:50.452: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17257): libfprint-device-DEBUG: 04:23:50.452: Device reported verify completion
(process:17257): libfprint-device-DEBUG: 04:23:50.452: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-device-DEBUG: 04:23:50.462: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17257): libfprint-device-DEBUG: 04:23:50.463: Updated temperature model after 0.01 seconds, ratio 0.32 -> 0.32, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-device-DEBUG: 04:23:50.464: Updated temperature model after 0.00 seconds, ratio 0.32 -> 0.32, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-image_device-DEBUG: 04:23:50.464: Activating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:50.464: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:50.465: Image device activation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:50.465: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17257): libfprint-image_device-DEBUG: 04:23:50.465: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17257): libfprint-device-DEBUG: 04:23:50.465: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17257): libfprint-image_device-DEBUG: 04:23:50.467: Deactivating image device
(process:17257): libfprint-image_device-DEBUG: 04:23:50.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17257): libfprint-image_device-DEBUG: 04:23:50.467: Image device deactivation completed
(process:17257): libfprint-image_device-DEBUG: 04:23:50.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17257): libfprint-device-DEBUG: 04:23:50.468: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY
(process:17257): libfprint-device-DEBUG: 04:23:50.468: Device reported verify completion
(process:17257): libfprint-device-DEBUG: 04:23:50.468: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17257): libfprint-device-DEBUG: 04:23:50.470: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17257): libfprint-device-DEBUG: 04:23:50.470: Updated temperature model after 0.01 seconds, ratio 0.32 -> 0.32, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17257): libfprint-virtual_image-DEBUG: 04:23:50.472: 38977930069894: ../libfprint/drivers/virtual-image.c:244
(process:17257): libfprint-image_device-DEBUG: 04:23:50.574: Image device close completed
(process:17257): libfprint-device-DEBUG: 04:23:50.574: Device reported close completion
(process:17257): libfprint-device-DEBUG: 04:23:50.574: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17257): libfprint-device-DEBUG: 04:23:50.575: Updated temperature model after 0.10 seconds, ratio 0.32 -> 0.32, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Enroll done
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Print was processed, continuing
Enroll done
fp - device - error - quark: An unspecified error occurred! (0)
ok
----------------------------------------------------------------------
Ran 1 test in 12.790s
OK
==============================================================================
=================================== 27/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_finger_status
start time: 04:23:50
duration: 0.95s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=229 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_finger_status
----------------------------------- stdout -----------------------------------
(process:17391): libfprint-context-DEBUG: 04:23:50.842: Initializing FpContext (libfprint version 1.94.6)
(process:17391): libfprint-context-DEBUG: 04:23:50.899: No driver found for USB device 1D6B:0003
(process:17391): libfprint-context-DEBUG: 04:23:50.899: No driver found for USB device 0BDA:5401
(process:17391): libfprint-context-DEBUG: 04:23:50.899: No driver found for USB device 1D6B:0002
(process:17391): libfprint-context-DEBUG: 04:23:50.899: No driver found for USB device 1D6B:0003
(process:17391): libfprint-context-DEBUG: 04:23:50.900: No driver found for USB device 0624:0249
(process:17391): libfprint-context-DEBUG: 04:23:50.900: No driver found for USB device 0624:0248
(process:17391): libfprint-context-DEBUG: 04:23:50.900: No driver found for USB device 1D6B:0002
(process:17391): libfprint-context-DEBUG: 04:23:50.900: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-i6huik7g/virtual-device.socket
(process:17391): libfprint-context-DEBUG: 04:23:50.902: created
(process:17391): libfprint-device-DEBUG: 04:23:50.921: Device reported probe completion
(process:17391): libfprint-device-DEBUG: 04:23:50.930: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17391): libfprint-device-DEBUG: 04:23:50.930: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:17391): libfprint-virtual_device-DEBUG: 04:23:50.933: 38977930531410: ../libfprint/drivers/virtual-device.c:387
(process:17391): libfprint-virtual_device_connection-DEBUG: 04:23:50.940: 38977930538191: ../libfprint/drivers/virtual-device-listener.c:153
(process:17391): libfprint-device-DEBUG: 04:23:50.948: Device reported open completion
(process:17391): libfprint-device-DEBUG: 04:23:50.948: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17391): libfprint-device-DEBUG: 04:23:50.948: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17391): libfprint-device-DEBUG: 04:23:50.964: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17391): libfprint-device-DEBUG: 04:23:50.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17391): libfprint-virtual_device_connection-DEBUG: 04:23:50.972: Got a new connection!
(process:17391): libfprint-virtual_device-DEBUG: 04:23:50.974: Got instructions of length 8
(process:17391): libfprint-virtual_device-DEBUG: 04:23:50.974: Received command FINGER 1
(process:17391): libfprint-virtual_device-DEBUG: 04:23:50.982: Processing command FINGER 1
(process:17391): libfprint-device-DEBUG: 04:23:50.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17391): libfprint-virtual_device_connection-DEBUG: 04:23:50.984: Got a new connection!
(process:17391): libfprint-virtual_device-DEBUG: 04:23:50.985: Got instructions of length 8
(process:17391): libfprint-virtual_device-DEBUG: 04:23:50.986: Received command FINGER 0
(process:17391): libfprint-virtual_device-DEBUG: 04:23:50.986: Processing command FINGER 0
(process:17391): libfprint-device-DEBUG: 04:23:50.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17391): libfprint-device-DEBUG: 04:23:50.987: Idle cancelling on ongoing operation!
(process:17391): libfprint-virtual_device-DEBUG: 04:23:50.988: Got cancellation!
(process:17391): libfprint-virtual_device-DEBUG: 04:23:50.988: Virtual device scan failed with error: Operation was cancelled
(process:17391): libfprint-device-DEBUG: 04:23:50.988: Device reported verify completion
(process:17391): libfprint-device-DEBUG: 04:23:50.988: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17391): libfprint-device-DEBUG: 04:23:50.988: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17391): libfprint-device-DEBUG: 04:23:50.989: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17391): libfprint-virtual_device_connection-DEBUG: 04:23:51.001: Got a new connection!
(process:17391): libfprint-virtual_device-DEBUG: 04:23:51.006: Got instructions of length 16
(process:17391): libfprint-virtual_device-DEBUG: 04:23:51.006: Received command SET_KEEP_ALIVE 0
(process:17391): libfprint-virtual_device-DEBUG: 04:23:51.006: Keep alive toggled: 0
(process:17391): libfprint-virtual_device_connection-DEBUG: 04:23:51.008: Got a new connection!
(process:17391): libfprint-virtual_device-DEBUG: 04:23:51.009: Got instructions of length 19
(process:17391): libfprint-virtual_device-DEBUG: 04:23:51.010: Received command SET_ENROLL_STAGES 5
(process:17391): libfprint-device-DEBUG: 04:23:51.015: Device reported close completion
(process:17391): libfprint-device-DEBUG: 04:23:51.016: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17391): libfprint-device-DEBUG: 04:23:51.016: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
----------------------------------------------------------------------
Ran 1 test in 0.204s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:732: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 28/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_finger_status_after_sleep
start time: 04:23:50
duration: 0.91s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=114 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_finger_status_after_sleep
----------------------------------- stdout -----------------------------------
(process:17393): libfprint-context-DEBUG: 04:23:50.887: Initializing FpContext (libfprint version 1.94.6)
(process:17393): libfprint-context-DEBUG: 04:23:50.934: No driver found for USB device 1D6B:0003
(process:17393): libfprint-context-DEBUG: 04:23:50.934: No driver found for USB device 0BDA:5401
(process:17393): libfprint-context-DEBUG: 04:23:50.934: No driver found for USB device 1D6B:0002
(process:17393): libfprint-context-DEBUG: 04:23:50.935: No driver found for USB device 1D6B:0003
(process:17393): libfprint-context-DEBUG: 04:23:50.935: No driver found for USB device 0624:0249
(process:17393): libfprint-context-DEBUG: 04:23:50.935: No driver found for USB device 0624:0248
(process:17393): libfprint-context-DEBUG: 04:23:50.935: No driver found for USB device 1D6B:0002
(process:17393): libfprint-context-DEBUG: 04:23:50.935: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-qecy6xqm/virtual-device.socket
(process:17393): libfprint-context-DEBUG: 04:23:50.937: created
(process:17393): libfprint-device-DEBUG: 04:23:50.956: Device reported probe completion
(process:17393): libfprint-device-DEBUG: 04:23:50.957: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17393): libfprint-device-DEBUG: 04:23:50.957: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:17393): libfprint-virtual_device-DEBUG: 04:23:50.968: 38977930566121: ../libfprint/drivers/virtual-device.c:387
(process:17393): libfprint-virtual_device_connection-DEBUG: 04:23:50.969: 38977930567451: ../libfprint/drivers/virtual-device-listener.c:153
(process:17393): libfprint-device-DEBUG: 04:23:50.972: Device reported open completion
(process:17393): libfprint-device-DEBUG: 04:23:50.973: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17393): libfprint-device-DEBUG: 04:23:50.973: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17393): libfprint-virtual_device_connection-DEBUG: 04:23:50.980: Got a new connection!
(process:17393): libfprint-virtual_device-DEBUG: 04:23:50.986: Got instructions of length 8
(process:17393): libfprint-virtual_device-DEBUG: 04:23:50.986: Received command SLEEP 10
(process:17393): libfprint-device-DEBUG: 04:23:50.998: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17393): libfprint-virtual_device-DEBUG: 04:23:50.999: Processing command SLEEP 10
(process:17393): libfprint-virtual_device-DEBUG: 04:23:50.999: Sleeping 10ms
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.010: Sleeping completed
(process:17393): libfprint-device-DEBUG: 04:23:51.010: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17393): libfprint-virtual_device_connection-DEBUG: 04:23:51.012: Got a new connection!
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.013: Got instructions of length 8
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.013: Received command FINGER 1
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.013: Processing command FINGER 1
(process:17393): libfprint-device-DEBUG: 04:23:51.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17393): libfprint-virtual_device_connection-DEBUG: 04:23:51.015: Got a new connection!
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.016: Got instructions of length 8
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.016: Received command FINGER 0
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.016: Processing command FINGER 0
(process:17393): libfprint-device-DEBUG: 04:23:51.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17393): libfprint-device-DEBUG: 04:23:51.028: Idle cancelling on ongoing operation!
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.029: Got cancellation!
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.029: Virtual device scan failed with error: Operation was cancelled
(process:17393): libfprint-device-DEBUG: 04:23:51.029: Device reported verify completion
(process:17393): libfprint-device-DEBUG: 04:23:51.029: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17393): libfprint-device-DEBUG: 04:23:51.029: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17393): libfprint-device-DEBUG: 04:23:51.030: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17393): libfprint-virtual_device_connection-DEBUG: 04:23:51.033: Got a new connection!
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.043: Got instructions of length 16
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.043: Received command SET_KEEP_ALIVE 0
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.043: Keep alive toggled: 0
(process:17393): libfprint-virtual_device_connection-DEBUG: 04:23:51.045: Got a new connection!
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.046: Got instructions of length 19
(process:17393): libfprint-virtual_device-DEBUG: 04:23:51.046: Received command SET_ENROLL_STAGES 5
(process:17393): libfprint-device-DEBUG: 04:23:51.048: Device reported close completion
(process:17393): libfprint-device-DEBUG: 04:23:51.048: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17393): libfprint-device-DEBUG: 04:23:51.048: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
----------------------------------------------------------------------
Ran 1 test in 0.202s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:749: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 29/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_identify_unsupported
start time: 04:23:50
duration: 0.83s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=99 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_identify_unsupported
----------------------------------- stdout -----------------------------------
(process:17395): libfprint-context-DEBUG: 04:23:50.977: Initializing FpContext (libfprint version 1.94.6)
(process:17395): libfprint-context-DEBUG: 04:23:51.032: No driver found for USB device 1D6B:0003
(process:17395): libfprint-context-DEBUG: 04:23:51.032: No driver found for USB device 0BDA:5401
(process:17395): libfprint-context-DEBUG: 04:23:51.032: No driver found for USB device 1D6B:0002
(process:17395): libfprint-context-DEBUG: 04:23:51.033: No driver found for USB device 1D6B:0003
(process:17395): libfprint-context-DEBUG: 04:23:51.033: No driver found for USB device 0624:0249
(process:17395): libfprint-context-DEBUG: 04:23:51.033: No driver found for USB device 0624:0248
(process:17395): libfprint-context-DEBUG: 04:23:51.033: No driver found for USB device 1D6B:0002
(process:17395): libfprint-context-DEBUG: 04:23:51.033: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-6hpr0evv/virtual-device.socket
(process:17395): libfprint-context-DEBUG: 04:23:51.035: created
(process:17395): libfprint-device-DEBUG: 04:23:51.054: Device reported probe completion
(process:17395): libfprint-device-DEBUG: 04:23:51.055: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17395): libfprint-device-DEBUG: 04:23:51.055: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:17395): libfprint-virtual_device-DEBUG: 04:23:51.066: 38977930664596: ../libfprint/drivers/virtual-device.c:387
(process:17395): libfprint-virtual_device_connection-DEBUG: 04:23:51.068: 38977930666003: ../libfprint/drivers/virtual-device-listener.c:153
(process:17395): libfprint-device-DEBUG: 04:23:51.071: Device reported open completion
(process:17395): libfprint-device-DEBUG: 04:23:51.071: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17395): libfprint-device-DEBUG: 04:23:51.071: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17395): libfprint-virtual_device_connection-DEBUG: 04:23:51.090: Got a new connection!
(process:17395): libfprint-virtual_device-DEBUG: 04:23:51.100: Got instructions of length 16
(process:17395): libfprint-virtual_device-DEBUG: 04:23:51.100: Received command SET_KEEP_ALIVE 0
(process:17395): libfprint-virtual_device-DEBUG: 04:23:51.100: Keep alive toggled: 0
(process:17395): libfprint-virtual_device_connection-DEBUG: 04:23:51.102: Got a new connection!
(process:17395): libfprint-virtual_device-DEBUG: 04:23:51.103: Got instructions of length 19
(process:17395): libfprint-virtual_device-DEBUG: 04:23:51.103: Received command SET_ENROLL_STAGES 5
(process:17395): libfprint-device-DEBUG: 04:23:51.105: Device reported close completion
(process:17395): libfprint-device-DEBUG: 04:23:51.105: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17395): libfprint-device-DEBUG: 04:23:51.105: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17395): libfprint-virtual_device-DEBUG: 04:23:51.115: 38977930713624: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.162s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:902: DeprecationWarning: FPrint.Device.supports_identify is deprecated
if self.dev.supports_identify():
==============================================================================
=================================== 30/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_open_error
start time: 04:23:50
duration: 0.97s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=49 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_open_error
----------------------------------- stdout -----------------------------------
(process:17397): libfprint-context-DEBUG: 04:23:51.422: Initializing FpContext (libfprint version 1.94.6)
(process:17397): libfprint-context-DEBUG: 04:23:51.478: No driver found for USB device 1D6B:0003
(process:17397): libfprint-context-DEBUG: 04:23:51.478: No driver found for USB device 0BDA:5401
(process:17397): libfprint-context-DEBUG: 04:23:51.478: No driver found for USB device 1D6B:0002
(process:17397): libfprint-context-DEBUG: 04:23:51.478: No driver found for USB device 1D6B:0003
(process:17397): libfprint-context-DEBUG: 04:23:51.479: No driver found for USB device 0624:0249
(process:17397): libfprint-context-DEBUG: 04:23:51.479: No driver found for USB device 0624:0248
(process:17397): libfprint-context-DEBUG: 04:23:51.479: No driver found for USB device 1D6B:0002
(process:17397): libfprint-context-DEBUG: 04:23:51.479: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-iaz4pvpz/virtual-device.socket
(process:17397): libfprint-context-DEBUG: 04:23:51.481: created
(process:17397): libfprint-device-DEBUG: 04:23:51.500: Device reported probe completion
(process:17397): libfprint-device-DEBUG: 04:23:51.501: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17397): libfprint-device-DEBUG: 04:23:51.501: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_open_error (__main__.VirtualDevice.test_open_error) ... (process:17397): libfprint-virtual_device-DEBUG: 04:23:51.512: 38977931110257: ../libfprint/drivers/virtual-device.c:387
(process:17397): libfprint-virtual_device_connection-DEBUG: 04:23:51.513: 38977931111598: ../libfprint/drivers/virtual-device-listener.c:153
(process:17397): libfprint-device-DEBUG: 04:23:51.520: Device reported open completion
(process:17397): libfprint-device-DEBUG: 04:23:51.521: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17397): libfprint-device-DEBUG: 04:23:51.521: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17397): libfprint-virtual_device_connection-DEBUG: 04:23:51.528: Got a new connection!
(process:17397): libfprint-virtual_device-DEBUG: 04:23:51.530: Got instructions of length 16
(process:17397): libfprint-virtual_device-DEBUG: 04:23:51.530: Received command IGNORED_COMMAND
(process:17397): libfprint-virtual_device_connection-DEBUG: 04:23:51.533: Got a new connection!
(process:17397): libfprint-virtual_device-DEBUG: 04:23:51.542: Got instructions of length 7
(process:17397): libfprint-virtual_device-DEBUG: 04:23:51.542: Received command ERROR 5
(process:17397): libfprint-virtual_device-DEBUG: 04:23:51.545: Processing command IGNORED_COMMAND
(process:17397): libfprint-device-DEBUG: 04:23:51.545: Device reported close completion
(process:17397): libfprint-device-DEBUG: 04:23:51.545: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17397): libfprint-device-DEBUG: 04:23:51.546: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17397): libfprint-virtual_device-DEBUG: 04:23:51.555: 38977931153475: ../libfprint/drivers/virtual-device.c:387
(process:17397): libfprint-virtual_device-DEBUG: 04:23:51.555: Processing command ERROR 5
(process:17397): libfprint-device-DEBUG: 04:23:51.556: Device reported open completion
(process:17397): libfprint-device-DEBUG: 04:23:51.556: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17397): libfprint-device-DEBUG: 04:23:51.557: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17397): libfprint-virtual_device-DEBUG: 04:23:51.559: 38977931156924: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.174s
OK
==============================================================================
=================================== 31/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_open_error_with_keep_alive
start time: 04:23:51
duration: 0.63s
result: exit status 0
command: G_DEBUG=fatal-warnings MALLOC_PERTURB_=163 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_open_error_with_keep_alive
----------------------------------- stdout -----------------------------------
(process:17408): libfprint-context-DEBUG: 04:23:51.591: Initializing FpContext (libfprint version 1.94.6)
(process:17408): libfprint-context-DEBUG: 04:23:51.623: No driver found for USB device 1D6B:0003
(process:17408): libfprint-context-DEBUG: 04:23:51.623: No driver found for USB device 0BDA:5401
(process:17408): libfprint-context-DEBUG: 04:23:51.624: No driver found for USB device 1D6B:0002
(process:17408): libfprint-context-DEBUG: 04:23:51.624: No driver found for USB device 1D6B:0003
(process:17408): libfprint-context-DEBUG: 04:23:51.625: No driver found for USB device 0624:0249
(process:17408): libfprint-context-DEBUG: 04:23:51.625: No driver found for USB device 0624:0248
(process:17408): libfprint-context-DEBUG: 04:23:51.626: No driver found for USB device 1D6B:0002
(process:17408): libfprint-context-DEBUG: 04:23:51.626: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-tb_aia1a/virtual-device.socket
(process:17408): libfprint-context-DEBUG: 04:23:51.628: created
(process:17408): libfprint-device-DEBUG: 04:23:51.640: Device reported probe completion
(process:17408): libfprint-device-DEBUG: 04:23:51.641: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17408): libfprint-device-DEBUG: 04:23:51.642: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:17408): libfprint-virtual_device-DEBUG: 04:23:51.645: 38977931243454: ../libfprint/drivers/virtual-device.c:387
(process:17408): libfprint-virtual_device_connection-DEBUG: 04:23:51.647: 38977931245292: ../libfprint/drivers/virtual-device-listener.c:153
(process:17408): libfprint-device-DEBUG: 04:23:51.665: Device reported open completion
(process:17408): libfprint-device-DEBUG: 04:23:51.666: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17408): libfprint-device-DEBUG: 04:23:51.666: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17408): libfprint-virtual_device_connection-DEBUG: 04:23:51.670: Got a new connection!
(process:17408): libfprint-virtual_device-DEBUG: 04:23:51.672: Got instructions of length 16
(process:17408): libfprint-virtual_device-DEBUG: 04:23:51.672: Received command SET_KEEP_ALIVE 1
(process:17408): libfprint-virtual_device-DEBUG: 04:23:51.673: Keep alive toggled: 1
(process:17408): libfprint-device-DEBUG: 04:23:51.674: Device reported close completion
(process:17408): libfprint-device-DEBUG: 04:23:51.675: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17408): libfprint-device-DEBUG: 04:23:51.675: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17408): libfprint-virtual_device_connection-DEBUG: 04:23:51.678: Got a new connection!
(process:17408): libfprint-virtual_device-DEBUG: 04:23:51.684: Got instructions of length 7
(process:17408): libfprint-virtual_device-DEBUG: 04:23:51.684: Received command ERROR 5
(process:17408): libfprint-virtual_device-DEBUG: 04:23:51.686: 38977931283810: ../libfprint/drivers/virtual-device.c:387
(process:17408): libfprint-virtual_device-DEBUG: 04:23:51.686: Processing command ERROR 5
(process:17408): libfprint-device-DEBUG: 04:23:51.687: Device reported open completion
(process:17408): libfprint-device-DEBUG: 04:23:51.687: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17408): libfprint-device-DEBUG: 04:23:51.688: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17408): libfprint-virtual_device-DEBUG: 04:23:51.694: 38977931292567: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.126s
OK
==============================================================================
=================================== 32/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDevice / VirtualDevice.test_quick_enroll
start time: 04:23:51
duration: 0.97s
result: exit status 0
command: G_DEBUG=fatal-warnings MALLOC_PERTURB_=166 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDevice.test_quick_enroll
----------------------------------- stdout -----------------------------------
(process:17410): libfprint-context-DEBUG: 04:23:51.878: Initializing FpContext (libfprint version 1.94.6)
(process:17410): libfprint-context-DEBUG: 04:23:51.935: No driver found for USB device 1D6B:0003
(process:17410): libfprint-context-DEBUG: 04:23:51.935: No driver found for USB device 0BDA:5401
(process:17410): libfprint-context-DEBUG: 04:23:51.935: No driver found for USB device 1D6B:0002
(process:17410): libfprint-context-DEBUG: 04:23:51.935: No driver found for USB device 1D6B:0003
(process:17410): libfprint-context-DEBUG: 04:23:51.936: No driver found for USB device 0624:0249
(process:17410): libfprint-context-DEBUG: 04:23:51.936: No driver found for USB device 0624:0248
(process:17410): libfprint-context-DEBUG: 04:23:51.936: No driver found for USB device 1D6B:0002
(process:17410): libfprint-context-DEBUG: 04:23:51.936: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-oren5ao0/virtual-device.socket
(process:17410): libfprint-context-DEBUG: 04:23:51.937: created
(process:17410): libfprint-device-DEBUG: 04:23:51.964: Device reported probe completion
(process:17410): libfprint-device-DEBUG: 04:23:51.965: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17410): libfprint-device-DEBUG: 04:23:51.965: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:17410): libfprint-virtual_device-DEBUG: 04:23:51.976: 38977931574344: ../libfprint/drivers/virtual-device.c:387
(process:17410): libfprint-virtual_device_connection-DEBUG: 04:23:51.977: 38977931575705: ../libfprint/drivers/virtual-device-listener.c:153
(process:17410): libfprint-device-DEBUG: 04:23:51.985: Device reported open completion
(process:17410): libfprint-device-DEBUG: 04:23:51.985: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17410): libfprint-device-DEBUG: 04:23:51.985: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17410): libfprint-virtual_device_connection-DEBUG: 04:23:51.992: Got a new connection!
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.002: Got instructions of length 19
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.002: Received command SET_ENROLL_STAGES 1
(process:17410): libfprint-virtual_device_connection-DEBUG: 04:23:52.006: Got a new connection!
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.007: Got instructions of length 14
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.007: Received command SCAN testprint
(process:17410): libfprint-device-DEBUG: 04:23:52.022: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.022: Processing command SCAN testprint
(process:17410): libfprint-device-DEBUG: 04:23:52.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17410): libfprint-device-DEBUG: 04:23:52.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17410): libfprint-device-DEBUG: 04:23:52.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17410): libfprint-device-DEBUG: 04:23:52.023: Device reported enroll progress, reported 1 of 1 have been completed
(process:17410): libfprint-device-DEBUG: 04:23:52.023: Device reported enroll completion
(process:17410): libfprint-device-DEBUG: 04:23:52.023: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17410): libfprint-device-DEBUG: 04:23:52.024: Print for finger FP_FINGER_LEFT_LITTLE enrolled
(process:17410): libfprint-device-DEBUG: 04:23:52.024: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17410): libfprint-device-DEBUG: 04:23:52.024: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17410): libfprint-virtual_device_connection-DEBUG: 04:23:52.035: Got a new connection!
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.036: Got instructions of length 16
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.036: Received command SET_KEEP_ALIVE 0
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.036: Keep alive toggled: 0
(process:17410): libfprint-virtual_device_connection-DEBUG: 04:23:52.046: Got a new connection!
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.048: Got instructions of length 19
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.048: Received command SET_ENROLL_STAGES 5
(process:17410): libfprint-device-DEBUG: 04:23:52.049: Device reported close completion
(process:17410): libfprint-device-DEBUG: 04:23:52.050: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17410): libfprint-device-DEBUG: 04:23:52.050: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
Enroll done
ok
(process:17410): libfprint-virtual_device-DEBUG: 04:23:52.052: 38977931650154: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.206s
OK
==============================================================================
=================================== 33/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_capture
start time: 04:23:51
duration: 1.08s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=9 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceBusyDeviceOperations.test_capture
----------------------------------- stdout -----------------------------------
(process:17412): libfprint-context-DEBUG: 04:23:51.881: Initializing FpContext (libfprint version 1.94.6)
(process:17412): libfprint-context-DEBUG: 04:23:51.934: No driver found for USB device 1D6B:0003
(process:17412): libfprint-context-DEBUG: 04:23:51.935: No driver found for USB device 0BDA:5401
(process:17412): libfprint-context-DEBUG: 04:23:51.935: No driver found for USB device 1D6B:0002
(process:17412): libfprint-context-DEBUG: 04:23:51.935: No driver found for USB device 1D6B:0003
(process:17412): libfprint-context-DEBUG: 04:23:51.935: No driver found for USB device 0624:0249
(process:17412): libfprint-context-DEBUG: 04:23:51.935: No driver found for USB device 0624:0248
(process:17412): libfprint-context-DEBUG: 04:23:51.935: No driver found for USB device 1D6B:0002
(process:17412): libfprint-context-DEBUG: 04:23:51.936: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-x48aht__/virtual-device.socket
(process:17412): libfprint-context-DEBUG: 04:23:51.937: created
(process:17412): libfprint-device-DEBUG: 04:23:51.953: Device reported probe completion
(process:17412): libfprint-device-DEBUG: 04:23:51.953: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17412): libfprint-device-DEBUG: 04:23:51.953: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:17412): libfprint-virtual_device-DEBUG: 04:23:51.966: 38977931563774: ../libfprint/drivers/virtual-device.c:387
(process:17412): libfprint-virtual_device_connection-DEBUG: 04:23:51.967: 38977931565387: ../libfprint/drivers/virtual-device-listener.c:153
(process:17412): libfprint-device-DEBUG: 04:23:51.970: Device reported open completion
(process:17412): libfprint-device-DEBUG: 04:23:51.971: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17412): libfprint-device-DEBUG: 04:23:51.972: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17412): libfprint-virtual_device_connection-DEBUG: 04:23:51.979: Got a new connection!
(process:17412): libfprint-virtual_device-DEBUG: 04:23:51.981: Got instructions of length 9
(process:17412): libfprint-virtual_device-DEBUG: 04:23:51.982: Received command SLEEP 200
(process:17412): libfprint-virtual_device-DEBUG: 04:23:51.988: Processing command SLEEP 200
(process:17412): libfprint-virtual_device-DEBUG: 04:23:51.989: Sleeping 200ms
(process:17412): libfprint-virtual_device-DEBUG: 04:23:52.194: Sleeping completed
(process:17412): libfprint-device-DEBUG: 04:23:52.194: Device reported close completion
(process:17412): libfprint-device-DEBUG: 04:23:52.195: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17412): libfprint-device-DEBUG: 04:23:52.195: Updated temperature model after 0.22 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17412): libfprint-virtual_device-DEBUG: 04:23:52.197: 38977931795010: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.342s
OK
==============================================================================
=================================== 34/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_close
start time: 04:23:51
duration: 0.82s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=132 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceBusyDeviceOperations.test_close
----------------------------------- stdout -----------------------------------
(process:17420): libfprint-context-DEBUG: 04:23:52.125: Initializing FpContext (libfprint version 1.94.6)
(process:17420): libfprint-context-DEBUG: 04:23:52.158: No driver found for USB device 1D6B:0003
(process:17420): libfprint-context-DEBUG: 04:23:52.159: No driver found for USB device 0BDA:5401
(process:17420): libfprint-context-DEBUG: 04:23:52.160: No driver found for USB device 1D6B:0002
(process:17420): libfprint-context-DEBUG: 04:23:52.160: No driver found for USB device 1D6B:0003
(process:17420): libfprint-context-DEBUG: 04:23:52.161: No driver found for USB device 0624:0249
(process:17420): libfprint-context-DEBUG: 04:23:52.161: No driver found for USB device 0624:0248
(process:17420): libfprint-context-DEBUG: 04:23:52.162: No driver found for USB device 1D6B:0002
(process:17420): libfprint-context-DEBUG: 04:23:52.163: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-p8ewc7ko/virtual-device.socket
(process:17420): libfprint-context-DEBUG: 04:23:52.164: created
(process:17420): libfprint-device-DEBUG: 04:23:52.185: Device reported probe completion
(process:17420): libfprint-device-DEBUG: 04:23:52.185: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17420): libfprint-device-DEBUG: 04:23:52.185: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:17420): libfprint-virtual_device-DEBUG: 04:23:52.188: 38977931786549: ../libfprint/drivers/virtual-device.c:387
(process:17420): libfprint-virtual_device_connection-DEBUG: 04:23:52.190: 38977931787994: ../libfprint/drivers/virtual-device-listener.c:153
(process:17420): libfprint-device-DEBUG: 04:23:52.194: Device reported open completion
(process:17420): libfprint-device-DEBUG: 04:23:52.195: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17420): libfprint-device-DEBUG: 04:23:52.196: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17420): libfprint-virtual_device_connection-DEBUG: 04:23:52.199: Got a new connection!
(process:17420): libfprint-virtual_device-DEBUG: 04:23:52.201: Got instructions of length 9
(process:17420): libfprint-virtual_device-DEBUG: 04:23:52.202: Received command SLEEP 200
(process:17420): libfprint-virtual_device-DEBUG: 04:23:52.204: Processing command SLEEP 200
(process:17420): libfprint-virtual_device-DEBUG: 04:23:52.205: Sleeping 200ms
(process:17420): libfprint-virtual_device-DEBUG: 04:23:52.410: Sleeping completed
(process:17420): libfprint-device-DEBUG: 04:23:52.410: Device reported close completion
(process:17420): libfprint-device-DEBUG: 04:23:52.411: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17420): libfprint-device-DEBUG: 04:23:52.411: Updated temperature model after 0.22 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17420): libfprint-virtual_device-DEBUG: 04:23:52.413: 38977932011288: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.307s
OK
==============================================================================
=================================== 35/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_delete_print
start time: 04:23:51
duration: 1.11s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=66 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceBusyDeviceOperations.test_delete_print
----------------------------------- stdout -----------------------------------
(process:17422): libfprint-context-DEBUG: 04:23:52.449: Initializing FpContext (libfprint version 1.94.6)
(process:17422): libfprint-context-DEBUG: 04:23:52.508: No driver found for USB device 1D6B:0003
(process:17422): libfprint-context-DEBUG: 04:23:52.509: No driver found for USB device 0BDA:5401
(process:17422): libfprint-context-DEBUG: 04:23:52.509: No driver found for USB device 1D6B:0002
(process:17422): libfprint-context-DEBUG: 04:23:52.509: No driver found for USB device 1D6B:0003
(process:17422): libfprint-context-DEBUG: 04:23:52.509: No driver found for USB device 0624:0249
(process:17422): libfprint-context-DEBUG: 04:23:52.510: No driver found for USB device 0624:0248
(process:17422): libfprint-context-DEBUG: 04:23:52.510: No driver found for USB device 1D6B:0002
(process:17422): libfprint-context-DEBUG: 04:23:52.510: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-6jqnay5b/virtual-device.socket
(process:17422): libfprint-context-DEBUG: 04:23:52.511: created
(process:17422): libfprint-device-DEBUG: 04:23:52.535: Device reported probe completion
(process:17422): libfprint-device-DEBUG: 04:23:52.536: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17422): libfprint-device-DEBUG: 04:23:52.536: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:17422): libfprint-virtual_device-DEBUG: 04:23:52.539: 38977932137033: ../libfprint/drivers/virtual-device.c:387
(process:17422): libfprint-virtual_device_connection-DEBUG: 04:23:52.540: 38977932138450: ../libfprint/drivers/virtual-device-listener.c:153
(process:17422): libfprint-device-DEBUG: 04:23:52.548: Device reported open completion
(process:17422): libfprint-device-DEBUG: 04:23:52.548: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17422): libfprint-device-DEBUG: 04:23:52.548: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17422): libfprint-virtual_device_connection-DEBUG: 04:23:52.558: Got a new connection!
(process:17422): libfprint-virtual_device-DEBUG: 04:23:52.559: Got instructions of length 9
(process:17422): libfprint-virtual_device-DEBUG: 04:23:52.560: Received command SLEEP 200
(process:17422): libfprint-virtual_device-DEBUG: 04:23:52.570: Processing command SLEEP 200
(process:17422): libfprint-virtual_device-DEBUG: 04:23:52.570: Sleeping 200ms
(process:17422): libfprint-virtual_device-DEBUG: 04:23:52.774: Sleeping completed
(process:17422): libfprint-device-DEBUG: 04:23:52.775: Device reported close completion
(process:17422): libfprint-device-DEBUG: 04:23:52.776: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17422): libfprint-device-DEBUG: 04:23:52.776: Updated temperature model after 0.23 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17422): libfprint-virtual_device-DEBUG: 04:23:52.779: 38977932377036: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.354s
OK
==============================================================================
=================================== 36/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_enroll
start time: 04:23:52
duration: 1.08s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=49 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceBusyDeviceOperations.test_enroll
----------------------------------- stdout -----------------------------------
(process:17433): libfprint-context-DEBUG: 04:23:52.814: Initializing FpContext (libfprint version 1.94.6)
(process:17433): libfprint-context-DEBUG: 04:23:52.866: No driver found for USB device 1D6B:0003
(process:17433): libfprint-context-DEBUG: 04:23:52.867: No driver found for USB device 0BDA:5401
(process:17433): libfprint-context-DEBUG: 04:23:52.867: No driver found for USB device 1D6B:0002
(process:17433): libfprint-context-DEBUG: 04:23:52.867: No driver found for USB device 1D6B:0003
(process:17433): libfprint-context-DEBUG: 04:23:52.867: No driver found for USB device 0624:0249
(process:17433): libfprint-context-DEBUG: 04:23:52.867: No driver found for USB device 0624:0248
(process:17433): libfprint-context-DEBUG: 04:23:52.867: No driver found for USB device 1D6B:0002
(process:17433): libfprint-context-DEBUG: 04:23:52.868: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-vewfnidd/virtual-device.socket
(process:17433): libfprint-context-DEBUG: 04:23:52.869: created
(process:17433): libfprint-device-DEBUG: 04:23:52.896: Device reported probe completion
(process:17433): libfprint-device-DEBUG: 04:23:52.897: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17433): libfprint-device-DEBUG: 04:23:52.897: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:17433): libfprint-virtual_device-DEBUG: 04:23:52.902: 38977932499924: ../libfprint/drivers/virtual-device.c:387
(process:17433): libfprint-virtual_device_connection-DEBUG: 04:23:52.918: 38977932516710: ../libfprint/drivers/virtual-device-listener.c:153
(process:17433): libfprint-device-DEBUG: 04:23:52.926: Device reported open completion
(process:17433): libfprint-device-DEBUG: 04:23:52.926: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17433): libfprint-device-DEBUG: 04:23:52.927: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17433): libfprint-virtual_device_connection-DEBUG: 04:23:52.930: Got a new connection!
(process:17433): libfprint-virtual_device-DEBUG: 04:23:52.932: Got instructions of length 9
(process:17433): libfprint-virtual_device-DEBUG: 04:23:52.932: Received command SLEEP 200
(process:17433): libfprint-virtual_device-DEBUG: 04:23:52.938: Processing command SLEEP 200
(process:17433): libfprint-virtual_device-DEBUG: 04:23:52.938: Sleeping 200ms
(process:17433): libfprint-virtual_device-DEBUG: 04:23:53.140: Sleeping completed
(process:17433): libfprint-device-DEBUG: 04:23:53.140: Device reported close completion
(process:17433): libfprint-device-DEBUG: 04:23:53.141: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17433): libfprint-device-DEBUG: 04:23:53.141: Updated temperature model after 0.21 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17433): libfprint-virtual_device-DEBUG: 04:23:53.143: 38977932740900: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.349s
OK
==============================================================================
=================================== 37/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_identify
start time: 04:23:52
duration: 1.08s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=252 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceBusyDeviceOperations.test_identify
----------------------------------- stdout -----------------------------------
(process:17435): libfprint-context-DEBUG: 04:23:52.919: Initializing FpContext (libfprint version 1.94.6)
(process:17435): libfprint-context-DEBUG: 04:23:52.972: No driver found for USB device 1D6B:0003
(process:17435): libfprint-context-DEBUG: 04:23:52.973: No driver found for USB device 0BDA:5401
(process:17435): libfprint-context-DEBUG: 04:23:52.973: No driver found for USB device 1D6B:0002
(process:17435): libfprint-context-DEBUG: 04:23:52.974: No driver found for USB device 1D6B:0003
(process:17435): libfprint-context-DEBUG: 04:23:52.974: No driver found for USB device 0624:0249
(process:17435): libfprint-context-DEBUG: 04:23:52.975: No driver found for USB device 0624:0248
(process:17435): libfprint-context-DEBUG: 04:23:52.975: No driver found for USB device 1D6B:0002
(process:17435): libfprint-context-DEBUG: 04:23:52.976: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-cvzwi92z/virtual-device.socket
(process:17435): libfprint-context-DEBUG: 04:23:52.977: created
(process:17435): libfprint-device-DEBUG: 04:23:52.999: Device reported probe completion
(process:17435): libfprint-device-DEBUG: 04:23:53.000: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17435): libfprint-device-DEBUG: 04:23:53.001: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:17435): libfprint-virtual_device-DEBUG: 04:23:53.013: 38977932611147: ../libfprint/drivers/virtual-device.c:387
(process:17435): libfprint-virtual_device_connection-DEBUG: 04:23:53.015: 38977932613168: ../libfprint/drivers/virtual-device-listener.c:153
(process:17435): libfprint-device-DEBUG: 04:23:53.018: Device reported open completion
(process:17435): libfprint-device-DEBUG: 04:23:53.019: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17435): libfprint-device-DEBUG: 04:23:53.020: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17435): libfprint-virtual_device_connection-DEBUG: 04:23:53.031: Got a new connection!
(process:17435): libfprint-virtual_device-DEBUG: 04:23:53.034: Got instructions of length 9
(process:17435): libfprint-virtual_device-DEBUG: 04:23:53.034: Received command SLEEP 200
(process:17435): libfprint-virtual_device-DEBUG: 04:23:53.037: Processing command SLEEP 200
(process:17435): libfprint-virtual_device-DEBUG: 04:23:53.037: Sleeping 200ms
(process:17435): libfprint-virtual_device-DEBUG: 04:23:53.239: Sleeping completed
(process:17435): libfprint-device-DEBUG: 04:23:53.239: Device reported close completion
(process:17435): libfprint-device-DEBUG: 04:23:53.240: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17435): libfprint-device-DEBUG: 04:23:53.240: Updated temperature model after 0.22 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17435): libfprint-virtual_device-DEBUG: 04:23:53.242: 38977932840134: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.341s
OK
==============================================================================
=================================== 38/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_list_prints
start time: 04:23:52
duration: 1.15s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests MALLOC_PERTURB_=120 FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceBusyDeviceOperations.test_list_prints
----------------------------------- stdout -----------------------------------
(process:17440): libfprint-context-DEBUG: 04:23:53.202: Initializing FpContext (libfprint version 1.94.6)
(process:17440): libfprint-context-DEBUG: 04:23:53.260: No driver found for USB device 1D6B:0003
(process:17440): libfprint-context-DEBUG: 04:23:53.260: No driver found for USB device 0BDA:5401
(process:17440): libfprint-context-DEBUG: 04:23:53.260: No driver found for USB device 1D6B:0002
(process:17440): libfprint-context-DEBUG: 04:23:53.260: No driver found for USB device 1D6B:0003
(process:17440): libfprint-context-DEBUG: 04:23:53.261: No driver found for USB device 0624:0249
(process:17440): libfprint-context-DEBUG: 04:23:53.261: No driver found for USB device 0624:0248
(process:17440): libfprint-context-DEBUG: 04:23:53.261: No driver found for USB device 1D6B:0002
(process:17440): libfprint-context-DEBUG: 04:23:53.261: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-y6jqip32/virtual-device.socket
(process:17440): libfprint-context-DEBUG: 04:23:53.267: created
(process:17440): libfprint-device-DEBUG: 04:23:53.296: Device reported probe completion
(process:17440): libfprint-device-DEBUG: 04:23:53.296: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17440): libfprint-device-DEBUG: 04:23:53.297: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:17440): libfprint-virtual_device-DEBUG: 04:23:53.300: 38977932898136: ../libfprint/drivers/virtual-device.c:387
(process:17440): libfprint-virtual_device_connection-DEBUG: 04:23:53.301: 38977932899471: ../libfprint/drivers/virtual-device-listener.c:153
(process:17440): libfprint-device-DEBUG: 04:23:53.312: Device reported open completion
(process:17440): libfprint-device-DEBUG: 04:23:53.312: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17440): libfprint-device-DEBUG: 04:23:53.313: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17440): libfprint-virtual_device_connection-DEBUG: 04:23:53.324: Got a new connection!
(process:17440): libfprint-virtual_device-DEBUG: 04:23:53.326: Got instructions of length 9
(process:17440): libfprint-virtual_device-DEBUG: 04:23:53.326: Received command SLEEP 200
(process:17440): libfprint-virtual_device-DEBUG: 04:23:53.332: Processing command SLEEP 200
(process:17440): libfprint-virtual_device-DEBUG: 04:23:53.332: Sleeping 200ms
(process:17440): libfprint-virtual_device-DEBUG: 04:23:53.538: Sleeping completed
(process:17440): libfprint-device-DEBUG: 04:23:53.538: Device reported close completion
(process:17440): libfprint-device-DEBUG: 04:23:53.539: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17440): libfprint-device-DEBUG: 04:23:53.540: Updated temperature model after 0.23 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17440): libfprint-virtual_device-DEBUG: 04:23:53.542: 38977933140247: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.366s
OK
==============================================================================
=================================== 39/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_capture
start time: 04:23:53
duration: 0.56s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb MALLOC_PERTURB_=232 G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceClosed.test_capture
----------------------------------- stdout -----------------------------------
(process:17455): libfprint-context-DEBUG: 04:23:53.780: Initializing FpContext (libfprint version 1.94.6)
(process:17455): libfprint-context-DEBUG: 04:23:53.812: No driver found for USB device 1D6B:0003
(process:17455): libfprint-context-DEBUG: 04:23:53.812: No driver found for USB device 0BDA:5401
(process:17455): libfprint-context-DEBUG: 04:23:53.812: No driver found for USB device 1D6B:0002
(process:17455): libfprint-context-DEBUG: 04:23:53.813: No driver found for USB device 1D6B:0003
(process:17455): libfprint-context-DEBUG: 04:23:53.813: No driver found for USB device 0624:0249
(process:17455): libfprint-context-DEBUG: 04:23:53.813: No driver found for USB device 0624:0248
(process:17455): libfprint-context-DEBUG: 04:23:53.813: No driver found for USB device 1D6B:0002
(process:17455): libfprint-context-DEBUG: 04:23:53.813: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-n8tf6899/virtual-device.socket
(process:17455): libfprint-context-DEBUG: 04:23:53.815: created
(process:17455): libfprint-device-DEBUG: 04:23:53.827: Device reported probe completion
(process:17455): libfprint-device-DEBUG: 04:23:53.827: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17455): libfprint-device-DEBUG: 04:23:53.827: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:17455): libfprint-virtual_device-DEBUG: 04:23:53.833: 38977933431166: ../libfprint/drivers/virtual-device.c:387
(process:17455): libfprint-virtual_device_connection-DEBUG: 04:23:53.834: 38977933432547: ../libfprint/drivers/virtual-device-listener.c:153
(process:17455): libfprint-device-DEBUG: 04:23:53.837: Device reported open completion
(process:17455): libfprint-device-DEBUG: 04:23:53.838: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17455): libfprint-device-DEBUG: 04:23:53.838: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17455): libfprint-device-DEBUG: 04:23:53.839: Device reported close completion
(process:17455): libfprint-device-DEBUG: 04:23:53.840: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17455): libfprint-device-DEBUG: 04:23:53.840: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17455): libfprint-virtual_device-DEBUG: 04:23:53.845: 38977933443568: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.087s
OK
==============================================================================
=================================== 40/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_open
start time: 04:23:52
duration: 1.24s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=116 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceBusyDeviceOperations.test_open
----------------------------------- stdout -----------------------------------
(process:17445): libfprint-context-DEBUG: 04:23:53.583: Initializing FpContext (libfprint version 1.94.6)
(process:17445): libfprint-context-DEBUG: 04:23:53.638: No driver found for USB device 1D6B:0003
(process:17445): libfprint-context-DEBUG: 04:23:53.639: No driver found for USB device 0BDA:5401
(process:17445): libfprint-context-DEBUG: 04:23:53.639: No driver found for USB device 1D6B:0002
(process:17445): libfprint-context-DEBUG: 04:23:53.640: No driver found for USB device 1D6B:0003
(process:17445): libfprint-context-DEBUG: 04:23:53.640: No driver found for USB device 0624:0249
(process:17445): libfprint-context-DEBUG: 04:23:53.640: No driver found for USB device 0624:0248
(process:17445): libfprint-context-DEBUG: 04:23:53.641: No driver found for USB device 1D6B:0002
(process:17445): libfprint-context-DEBUG: 04:23:53.641: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-ndqb8i9h/virtual-device.socket
(process:17445): libfprint-context-DEBUG: 04:23:53.643: created
(process:17445): libfprint-device-DEBUG: 04:23:53.671: Device reported probe completion
(process:17445): libfprint-device-DEBUG: 04:23:53.672: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17445): libfprint-device-DEBUG: 04:23:53.672: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:17445): libfprint-virtual_device-DEBUG: 04:23:53.687: 38977933285347: ../libfprint/drivers/virtual-device.c:387
(process:17445): libfprint-virtual_device_connection-DEBUG: 04:23:53.688: 38977933286700: ../libfprint/drivers/virtual-device-listener.c:153
(process:17445): libfprint-device-DEBUG: 04:23:53.699: Device reported open completion
(process:17445): libfprint-device-DEBUG: 04:23:53.699: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17445): libfprint-device-DEBUG: 04:23:53.699: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17445): libfprint-virtual_device_connection-DEBUG: 04:23:53.702: Got a new connection!
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.704: Got instructions of length 9
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.705: Received command SLEEP 200
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.711: Processing command SLEEP 200
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.712: Sleeping 200ms
(process:17445): libfprint-virtual_device_connection-DEBUG: 04:23:53.714: Got a new connection!
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.715: Got instructions of length 16
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.715: Received command SET_KEEP_ALIVE 1
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.716: Keep alive toggled: 1
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.914: Sleeping completed
(process:17445): libfprint-device-DEBUG: 04:23:53.914: Device reported close completion
(process:17445): libfprint-device-DEBUG: 04:23:53.914: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17445): libfprint-device-DEBUG: 04:23:53.915: Updated temperature model after 0.22 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17445): libfprint-virtual_device_connection-DEBUG: 04:23:53.916: Got a new connection!
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.917: Got instructions of length 9
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.917: Received command SLEEP 100
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.919: 38977933517476: ../libfprint/drivers/virtual-device.c:387
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.919: Processing command SLEEP 100
(process:17445): libfprint-virtual_device-DEBUG: 04:23:53.919: Sleeping 100ms
(process:17445): libfprint-virtual_device-DEBUG: 04:23:54.022: Sleeping completed
(process:17445): libfprint-virtual_device-DEBUG: 04:23:54.022: 38977933620310: ../libfprint/drivers/virtual-device.c:387
(process:17445): libfprint-device-DEBUG: 04:23:54.022: Device reported open completion
(process:17445): libfprint-device-DEBUG: 04:23:54.023: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17445): libfprint-device-DEBUG: 04:23:54.023: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17445): libfprint-device-DEBUG: 04:23:54.024: Device reported close completion
(process:17445): libfprint-device-DEBUG: 04:23:54.024: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17445): libfprint-device-DEBUG: 04:23:54.024: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17445): libfprint-virtual_device-DEBUG: 04:23:54.026: 38977933624433: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.468s
OK
==============================================================================
=================================== 41/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceBusyDeviceOperations / VirtualDeviceBusyDeviceOperations.test_verify
start time: 04:23:53
duration: 1.16s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=20 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceBusyDeviceOperations.test_verify
----------------------------------- stdout -----------------------------------
(process:17453): libfprint-context-DEBUG: 04:23:53.980: Initializing FpContext (libfprint version 1.94.6)
(process:17453): libfprint-context-DEBUG: 04:23:54.032: No driver found for USB device 1D6B:0003
(process:17453): libfprint-context-DEBUG: 04:23:54.032: No driver found for USB device 0BDA:5401
(process:17453): libfprint-context-DEBUG: 04:23:54.032: No driver found for USB device 1D6B:0002
(process:17453): libfprint-context-DEBUG: 04:23:54.033: No driver found for USB device 1D6B:0003
(process:17453): libfprint-context-DEBUG: 04:23:54.033: No driver found for USB device 0624:0249
(process:17453): libfprint-context-DEBUG: 04:23:54.033: No driver found for USB device 0624:0248
(process:17453): libfprint-context-DEBUG: 04:23:54.033: No driver found for USB device 1D6B:0002
(process:17453): libfprint-context-DEBUG: 04:23:54.033: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-xz4sblt_/virtual-device.socket
(process:17453): libfprint-context-DEBUG: 04:23:54.035: created
(process:17453): libfprint-device-DEBUG: 04:23:54.051: Device reported probe completion
(process:17453): libfprint-device-DEBUG: 04:23:54.051: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17453): libfprint-device-DEBUG: 04:23:54.052: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:17453): libfprint-virtual_device-DEBUG: 04:23:54.067: 38977933665271: ../libfprint/drivers/virtual-device.c:387
(process:17453): libfprint-virtual_device_connection-DEBUG: 04:23:54.068: 38977933666736: ../libfprint/drivers/virtual-device-listener.c:153
(process:17453): libfprint-device-DEBUG: 04:23:54.072: Device reported open completion
(process:17453): libfprint-device-DEBUG: 04:23:54.072: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17453): libfprint-device-DEBUG: 04:23:54.072: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17453): libfprint-virtual_device_connection-DEBUG: 04:23:54.083: Got a new connection!
(process:17453): libfprint-virtual_device-DEBUG: 04:23:54.085: Got instructions of length 9
(process:17453): libfprint-virtual_device-DEBUG: 04:23:54.085: Received command SLEEP 200
(process:17453): libfprint-virtual_device-DEBUG: 04:23:54.088: Processing command SLEEP 200
(process:17453): libfprint-virtual_device-DEBUG: 04:23:54.088: Sleeping 200ms
(process:17453): libfprint-virtual_device-DEBUG: 04:23:54.290: Sleeping completed
(process:17453): libfprint-device-DEBUG: 04:23:54.291: Device reported close completion
(process:17453): libfprint-device-DEBUG: 04:23:54.291: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17453): libfprint-device-DEBUG: 04:23:54.292: Updated temperature model after 0.22 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17453): libfprint-virtual_device-DEBUG: 04:23:54.293: 38977933891632: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.331s
OK
==============================================================================
=================================== 42/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_close
start time: 04:23:53
duration: 0.91s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=126 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceClosed.test_close
----------------------------------- stdout -----------------------------------
(process:17460): libfprint-context-DEBUG: 04:23:54.342: Initializing FpContext (libfprint version 1.94.6)
(process:17460): libfprint-context-DEBUG: 04:23:54.394: No driver found for USB device 1D6B:0003
(process:17460): libfprint-context-DEBUG: 04:23:54.395: No driver found for USB device 0BDA:5401
(process:17460): libfprint-context-DEBUG: 04:23:54.395: No driver found for USB device 1D6B:0002
(process:17460): libfprint-context-DEBUG: 04:23:54.396: No driver found for USB device 1D6B:0003
(process:17460): libfprint-context-DEBUG: 04:23:54.396: No driver found for USB device 0624:0249
(process:17460): libfprint-context-DEBUG: 04:23:54.397: No driver found for USB device 0624:0248
(process:17460): libfprint-context-DEBUG: 04:23:54.397: No driver found for USB device 1D6B:0002
(process:17460): libfprint-context-DEBUG: 04:23:54.398: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-duqo02eg/virtual-device.socket
(process:17460): libfprint-context-DEBUG: 04:23:54.400: created
(process:17460): libfprint-device-DEBUG: 04:23:54.436: Device reported probe completion
(process:17460): libfprint-device-DEBUG: 04:23:54.437: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17460): libfprint-device-DEBUG: 04:23:54.437: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_close (__main__.VirtualDeviceClosed.test_close) ... (process:17460): libfprint-virtual_device-DEBUG: 04:23:54.442: 38977934040100: ../libfprint/drivers/virtual-device.c:387
(process:17460): libfprint-virtual_device_connection-DEBUG: 04:23:54.444: 38977934041779: ../libfprint/drivers/virtual-device-listener.c:153
(process:17460): libfprint-device-DEBUG: 04:23:54.455: Device reported open completion
(process:17460): libfprint-device-DEBUG: 04:23:54.456: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17460): libfprint-device-DEBUG: 04:23:54.456: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17460): libfprint-device-DEBUG: 04:23:54.458: Device reported close completion
(process:17460): libfprint-device-DEBUG: 04:23:54.459: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17460): libfprint-device-DEBUG: 04:23:54.459: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17460): libfprint-virtual_device-DEBUG: 04:23:54.464: 38977934062131: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.150s
OK
==============================================================================
=================================== 43/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_delete_print
start time: 04:23:53
duration: 0.90s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=150 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceClosed.test_delete_print
----------------------------------- stdout -----------------------------------
(process:17465): libfprint-context-DEBUG: 04:23:54.608: Initializing FpContext (libfprint version 1.94.6)
(process:17465): libfprint-context-DEBUG: 04:23:54.669: No driver found for USB device 1D6B:0003
(process:17465): libfprint-context-DEBUG: 04:23:54.670: No driver found for USB device 0BDA:5401
(process:17465): libfprint-context-DEBUG: 04:23:54.670: No driver found for USB device 1D6B:0002
(process:17465): libfprint-context-DEBUG: 04:23:54.670: No driver found for USB device 1D6B:0003
(process:17465): libfprint-context-DEBUG: 04:23:54.670: No driver found for USB device 0624:0249
(process:17465): libfprint-context-DEBUG: 04:23:54.670: No driver found for USB device 0624:0248
(process:17465): libfprint-context-DEBUG: 04:23:54.671: No driver found for USB device 1D6B:0002
(process:17465): libfprint-context-DEBUG: 04:23:54.671: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-xf_42iiw/virtual-device.socket
(process:17465): libfprint-context-DEBUG: 04:23:54.672: created
(process:17465): libfprint-device-DEBUG: 04:23:54.700: Device reported probe completion
(process:17465): libfprint-device-DEBUG: 04:23:54.701: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17465): libfprint-device-DEBUG: 04:23:54.701: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:17465): libfprint-virtual_device-DEBUG: 04:23:54.704: 38977934302541: ../libfprint/drivers/virtual-device.c:387
(process:17465): libfprint-virtual_device_connection-DEBUG: 04:23:54.714: 38977934312339: ../libfprint/drivers/virtual-device-listener.c:153
(process:17465): libfprint-device-DEBUG: 04:23:54.718: Device reported open completion
(process:17465): libfprint-device-DEBUG: 04:23:54.718: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17465): libfprint-device-DEBUG: 04:23:54.719: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17465): libfprint-device-DEBUG: 04:23:54.720: Device reported close completion
(process:17465): libfprint-device-DEBUG: 04:23:54.721: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17465): libfprint-device-DEBUG: 04:23:54.722: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17465): libfprint-virtual_device-DEBUG: 04:23:54.738: 38977934336129: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.163s
OK
==============================================================================
=================================== 44/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_enroll
start time: 04:23:54
duration: 0.87s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=158 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceClosed.test_enroll
----------------------------------- stdout -----------------------------------
(process:17470): libfprint-context-DEBUG: 04:23:54.809: Initializing FpContext (libfprint version 1.94.6)
(process:17470): libfprint-context-DEBUG: 04:23:54.867: No driver found for USB device 1D6B:0003
(process:17470): libfprint-context-DEBUG: 04:23:54.867: No driver found for USB device 0BDA:5401
(process:17470): libfprint-context-DEBUG: 04:23:54.867: No driver found for USB device 1D6B:0002
(process:17470): libfprint-context-DEBUG: 04:23:54.868: No driver found for USB device 1D6B:0003
(process:17470): libfprint-context-DEBUG: 04:23:54.868: No driver found for USB device 0624:0249
(process:17470): libfprint-context-DEBUG: 04:23:54.868: No driver found for USB device 0624:0248
(process:17470): libfprint-context-DEBUG: 04:23:54.868: No driver found for USB device 1D6B:0002
(process:17470): libfprint-context-DEBUG: 04:23:54.868: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-a5c6nwzz/virtual-device.socket
(process:17470): libfprint-context-DEBUG: 04:23:54.870: created
(process:17470): libfprint-device-DEBUG: 04:23:54.889: Device reported probe completion
(process:17470): libfprint-device-DEBUG: 04:23:54.890: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17470): libfprint-device-DEBUG: 04:23:54.890: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:17470): libfprint-virtual_device-DEBUG: 04:23:54.893: 38977934491016: ../libfprint/drivers/virtual-device.c:387
(process:17470): libfprint-virtual_device_connection-DEBUG: 04:23:54.899: 38977934496940: ../libfprint/drivers/virtual-device-listener.c:153
(process:17470): libfprint-device-DEBUG: 04:23:54.902: Device reported open completion
(process:17470): libfprint-device-DEBUG: 04:23:54.902: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17470): libfprint-device-DEBUG: 04:23:54.902: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17470): libfprint-device-DEBUG: 04:23:54.903: Device reported close completion
(process:17470): libfprint-device-DEBUG: 04:23:54.904: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17470): libfprint-device-DEBUG: 04:23:54.904: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17470): libfprint-virtual_device-DEBUG: 04:23:54.921: 38977934519013: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.135s
OK
==============================================================================
=================================== 45/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_identify
start time: 04:23:54
duration: 0.85s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=41 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceClosed.test_identify
----------------------------------- stdout -----------------------------------
(process:17475): libfprint-context-DEBUG: 04:23:55.055: Initializing FpContext (libfprint version 1.94.6)
(process:17475): libfprint-context-DEBUG: 04:23:55.098: No driver found for USB device 1D6B:0003
(process:17475): libfprint-context-DEBUG: 04:23:55.098: No driver found for USB device 0BDA:5401
(process:17475): libfprint-context-DEBUG: 04:23:55.098: No driver found for USB device 1D6B:0002
(process:17475): libfprint-context-DEBUG: 04:23:55.099: No driver found for USB device 1D6B:0003
(process:17475): libfprint-context-DEBUG: 04:23:55.099: No driver found for USB device 0624:0249
(process:17475): libfprint-context-DEBUG: 04:23:55.099: No driver found for USB device 0624:0248
(process:17475): libfprint-context-DEBUG: 04:23:55.099: No driver found for USB device 1D6B:0002
(process:17475): libfprint-context-DEBUG: 04:23:55.099: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-67yd3rpt/virtual-device.socket
(process:17475): libfprint-context-DEBUG: 04:23:55.101: created
(process:17475): libfprint-device-DEBUG: 04:23:55.117: Device reported probe completion
(process:17475): libfprint-device-DEBUG: 04:23:55.117: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17475): libfprint-device-DEBUG: 04:23:55.126: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:17475): libfprint-virtual_device-DEBUG: 04:23:55.130: 38977934728289: ../libfprint/drivers/virtual-device.c:387
(process:17475): libfprint-virtual_device_connection-DEBUG: 04:23:55.132: 38977934729970: ../libfprint/drivers/virtual-device-listener.c:153
(process:17475): libfprint-device-DEBUG: 04:23:55.135: Device reported open completion
(process:17475): libfprint-device-DEBUG: 04:23:55.136: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17475): libfprint-device-DEBUG: 04:23:55.136: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17475): libfprint-device-DEBUG: 04:23:55.138: Device reported close completion
(process:17475): libfprint-device-DEBUG: 04:23:55.143: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17475): libfprint-device-DEBUG: 04:23:55.143: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17475): libfprint-virtual_device-DEBUG: 04:23:55.160: 38977934757960: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.128s
OK
==============================================================================
=================================== 46/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_list_prints
start time: 04:23:54
duration: 0.80s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=20 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceClosed.test_list_prints
----------------------------------- stdout -----------------------------------
(process:17477): libfprint-context-DEBUG: 04:23:55.227: Initializing FpContext (libfprint version 1.94.6)
(process:17477): libfprint-context-DEBUG: 04:23:55.283: No driver found for USB device 1D6B:0003
(process:17477): libfprint-context-DEBUG: 04:23:55.283: No driver found for USB device 0BDA:5401
(process:17477): libfprint-context-DEBUG: 04:23:55.283: No driver found for USB device 1D6B:0002
(process:17477): libfprint-context-DEBUG: 04:23:55.284: No driver found for USB device 1D6B:0003
(process:17477): libfprint-context-DEBUG: 04:23:55.284: No driver found for USB device 0624:0249
(process:17477): libfprint-context-DEBUG: 04:23:55.284: No driver found for USB device 0624:0248
(process:17477): libfprint-context-DEBUG: 04:23:55.284: No driver found for USB device 1D6B:0002
(process:17477): libfprint-context-DEBUG: 04:23:55.284: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-b6jkinuf/virtual-device.socket
(process:17477): libfprint-context-DEBUG: 04:23:55.286: created
(process:17477): libfprint-device-DEBUG: 04:23:55.299: Device reported probe completion
(process:17477): libfprint-device-DEBUG: 04:23:55.299: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17477): libfprint-device-DEBUG: 04:23:55.299: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:17477): libfprint-virtual_device-DEBUG: 04:23:55.302: 38977934900637: ../libfprint/drivers/virtual-device.c:387
(process:17477): libfprint-virtual_device_connection-DEBUG: 04:23:55.304: 38977934901995: ../libfprint/drivers/virtual-device-listener.c:153
(process:17477): libfprint-device-DEBUG: 04:23:55.307: Device reported open completion
(process:17477): libfprint-device-DEBUG: 04:23:55.307: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17477): libfprint-device-DEBUG: 04:23:55.307: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17477): libfprint-device-DEBUG: 04:23:55.309: Device reported close completion
(process:17477): libfprint-device-DEBUG: 04:23:55.309: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17477): libfprint-device-DEBUG: 04:23:55.310: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17477): libfprint-virtual_device-DEBUG: 04:23:55.316: 38977934914680: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.104s
OK
==============================================================================
=================================== 47/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceClosed / VirtualDeviceClosed.test_verify
start time: 04:23:54
duration: 0.85s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all MALLOC_PERTURB_=226 G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceClosed.test_verify
----------------------------------- stdout -----------------------------------
(process:17484): libfprint-context-DEBUG: 04:23:55.465: Initializing FpContext (libfprint version 1.94.6)
(process:17484): libfprint-context-DEBUG: 04:23:55.517: No driver found for USB device 1D6B:0003
(process:17484): libfprint-context-DEBUG: 04:23:55.517: No driver found for USB device 0BDA:5401
(process:17484): libfprint-context-DEBUG: 04:23:55.518: No driver found for USB device 1D6B:0002
(process:17484): libfprint-context-DEBUG: 04:23:55.526: No driver found for USB device 1D6B:0003
(process:17484): libfprint-context-DEBUG: 04:23:55.526: No driver found for USB device 0624:0249
(process:17484): libfprint-context-DEBUG: 04:23:55.526: No driver found for USB device 0624:0248
(process:17484): libfprint-context-DEBUG: 04:23:55.527: No driver found for USB device 1D6B:0002
(process:17484): libfprint-context-DEBUG: 04:23:55.527: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-0ljqyu8i/virtual-device.socket
(process:17484): libfprint-context-DEBUG: 04:23:55.528: created
(process:17484): libfprint-device-DEBUG: 04:23:55.555: Device reported probe completion
(process:17484): libfprint-device-DEBUG: 04:23:55.555: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17484): libfprint-device-DEBUG: 04:23:55.556: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:17484): libfprint-virtual_device-DEBUG: 04:23:55.559: 38977935156764: ../libfprint/drivers/virtual-device.c:387
(process:17484): libfprint-virtual_device_connection-DEBUG: 04:23:55.560: 38977935158502: ../libfprint/drivers/virtual-device-listener.c:153
(process:17484): libfprint-device-DEBUG: 04:23:55.572: Device reported open completion
(process:17484): libfprint-device-DEBUG: 04:23:55.573: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17484): libfprint-device-DEBUG: 04:23:55.573: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17484): libfprint-device-DEBUG: 04:23:55.575: Device reported close completion
(process:17484): libfprint-device-DEBUG: 04:23:55.575: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17484): libfprint-device-DEBUG: 04:23:55.576: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17484): libfprint-virtual_device-DEBUG: 04:23:55.592: 38977935190700: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.158s
OK
==============================================================================
=================================== 48/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_change_scan_type
start time: 04:23:55
duration: 0.54s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=80 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_change_scan_type
----------------------------------- stdout -----------------------------------
(process:17497): libfprint-context-DEBUG: 04:23:55.757: Initializing FpContext (libfprint version 1.94.6)
(process:17497): libfprint-context-DEBUG: 04:23:55.787: No driver found for USB device 1D6B:0003
(process:17497): libfprint-context-DEBUG: 04:23:55.788: No driver found for USB device 0BDA:5401
(process:17497): libfprint-context-DEBUG: 04:23:55.788: No driver found for USB device 1D6B:0002
(process:17497): libfprint-context-DEBUG: 04:23:55.788: No driver found for USB device 1D6B:0003
(process:17497): libfprint-context-DEBUG: 04:23:55.788: No driver found for USB device 0624:0249
(process:17497): libfprint-context-DEBUG: 04:23:55.788: No driver found for USB device 0624:0248
(process:17497): libfprint-context-DEBUG: 04:23:55.789: No driver found for USB device 1D6B:0002
(process:17497): libfprint-context-DEBUG: 04:23:55.789: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-wfm5yrs3/virtual-device-storage.socket
(process:17497): libfprint-context-DEBUG: 04:23:55.790: created
(process:17497): libfprint-device-DEBUG: 04:23:55.802: Device reported probe completion
(process:17497): libfprint-device-DEBUG: 04:23:55.803: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17497): libfprint-device-DEBUG: 04:23:55.803: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:17497): libfprint-virtual_device-DEBUG: 04:23:55.806: 38977935404583: ../libfprint/drivers/virtual-device.c:387
(process:17497): libfprint-virtual_device_connection-DEBUG: 04:23:55.808: 38977935405846: ../libfprint/drivers/virtual-device-listener.c:153
(process:17497): libfprint-device-DEBUG: 04:23:55.812: Device reported open completion
(process:17497): libfprint-device-DEBUG: 04:23:55.812: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17497): libfprint-device-DEBUG: 04:23:55.813: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17497): libfprint-virtual_device_connection-DEBUG: 04:23:55.818: Got a new connection!
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.821: Got instructions of length 19
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.821: Received command SET_SCAN_TYPE press
(process:17497): libfprint-virtual_device_connection-DEBUG: 04:23:55.824: Got a new connection!
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.826: Got instructions of length 19
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.826: Received command SET_SCAN_TYPE swipe
(process:17497): libfprint-virtual_device_connection-DEBUG: 04:23:55.830: Got a new connection!
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.831: Got instructions of length 25
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.832: Received command SET_SCAN_TYPE eye-contact
(process:17497): libfprint-virtual_device_connection-DEBUG: 04:23:55.839: Got a new connection!
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.840: Got instructions of length 5
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.841: Received command CONT
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.842: Processing command CONT
(process:17497): libfprint-device-DEBUG: 04:23:55.843: Device reported deletion completion
(process:17497): libfprint-device-DEBUG: 04:23:55.843: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17497): libfprint-device-DEBUG: 04:23:55.844: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17497): libfprint-virtual_device_connection-DEBUG: 04:23:55.846: Got a new connection!
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.847: Got instructions of length 16
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.848: Received command SET_KEEP_ALIVE 0
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.848: Keep alive toggled: 0
(process:17497): libfprint-virtual_device_connection-DEBUG: 04:23:55.850: Got a new connection!
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.852: Got instructions of length 19
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.852: Received command SET_ENROLL_STAGES 5
(process:17497): libfprint-device-DEBUG: 04:23:55.854: Device reported close completion
(process:17497): libfprint-device-DEBUG: 04:23:55.855: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17497): libfprint-device-DEBUG: 04:23:55.856: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17497): libfprint-virtual_device_storage-DEBUG: 04:23:55.858: 38977935456300: ../libfprint/drivers/virtual-device-storage.c:253
(process:17497): libfprint-virtual_device-DEBUG: 04:23:55.859: 38977935456772: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.114s
OK
==============================================================================
=================================== 49/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_capture_unsupported
start time: 04:23:55
duration: 0.91s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=5 FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_capture_unsupported
----------------------------------- stdout -----------------------------------
(process:17487): libfprint-context-DEBUG: 04:23:55.657: Initializing FpContext (libfprint version 1.94.6)
(process:17487): libfprint-context-DEBUG: 04:23:55.713: No driver found for USB device 1D6B:0003
(process:17487): libfprint-context-DEBUG: 04:23:55.713: No driver found for USB device 0BDA:5401
(process:17487): libfprint-context-DEBUG: 04:23:55.713: No driver found for USB device 1D6B:0002
(process:17487): libfprint-context-DEBUG: 04:23:55.713: No driver found for USB device 1D6B:0003
(process:17487): libfprint-context-DEBUG: 04:23:55.713: No driver found for USB device 0624:0249
(process:17487): libfprint-context-DEBUG: 04:23:55.714: No driver found for USB device 0624:0248
(process:17487): libfprint-context-DEBUG: 04:23:55.714: No driver found for USB device 1D6B:0002
(process:17487): libfprint-context-DEBUG: 04:23:55.714: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-460ogxee/virtual-device-storage.socket
(process:17487): libfprint-context-DEBUG: 04:23:55.715: created
(process:17487): libfprint-device-DEBUG: 04:23:55.751: Device reported probe completion
(process:17487): libfprint-device-DEBUG: 04:23:55.752: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17487): libfprint-device-DEBUG: 04:23:55.752: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:17487): libfprint-virtual_device-DEBUG: 04:23:55.755: 38977935353400: ../libfprint/drivers/virtual-device.c:387
(process:17487): libfprint-virtual_device_connection-DEBUG: 04:23:55.756: 38977935354709: ../libfprint/drivers/virtual-device-listener.c:153
(process:17487): libfprint-device-DEBUG: 04:23:55.763: Device reported open completion
(process:17487): libfprint-device-DEBUG: 04:23:55.764: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17487): libfprint-device-DEBUG: 04:23:55.765: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17487): libfprint-virtual_device_connection-DEBUG: 04:23:55.775: Got a new connection!
(process:17487): libfprint-virtual_device-DEBUG: 04:23:55.777: Got instructions of length 5
(process:17487): libfprint-virtual_device-DEBUG: 04:23:55.777: Received command CONT
(process:17487): libfprint-virtual_device-DEBUG: 04:23:55.779: Processing command CONT
(process:17487): libfprint-device-DEBUG: 04:23:55.779: Device reported deletion completion
(process:17487): libfprint-device-DEBUG: 04:23:55.780: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17487): libfprint-device-DEBUG: 04:23:55.780: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17487): libfprint-virtual_device_connection-DEBUG: 04:23:55.786: Got a new connection!
(process:17487): libfprint-virtual_device-DEBUG: 04:23:55.789: Got instructions of length 16
(process:17487): libfprint-virtual_device-DEBUG: 04:23:55.789: Received command SET_KEEP_ALIVE 0
(process:17487): libfprint-virtual_device-DEBUG: 04:23:55.790: Keep alive toggled: 0
(process:17487): libfprint-virtual_device_connection-DEBUG: 04:23:55.792: Got a new connection!
(process:17487): libfprint-virtual_device-DEBUG: 04:23:55.804: Got instructions of length 19
(process:17487): libfprint-virtual_device-DEBUG: 04:23:55.804: Received command SET_ENROLL_STAGES 5
(process:17487): libfprint-device-DEBUG: 04:23:55.806: Device reported close completion
(process:17487): libfprint-device-DEBUG: 04:23:55.807: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17487): libfprint-device-DEBUG: 04:23:55.808: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17487): libfprint-virtual_device_storage-DEBUG: 04:23:55.809: 38977935407566: ../libfprint/drivers/virtual-device-storage.c:253
(process:17487): libfprint-virtual_device-DEBUG: 04:23:55.809: 38977935407698: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.178s
OK
==============================================================================
=================================== 50/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_change_enroll_stages
start time: 04:23:55
duration: 0.97s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=50 FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_change_enroll_stages
----------------------------------- stdout -----------------------------------
(process:17493): libfprint-context-DEBUG: 04:23:55.926: Initializing FpContext (libfprint version 1.94.6)
(process:17493): libfprint-context-DEBUG: 04:23:55.991: No driver found for USB device 1D6B:0003
(process:17493): libfprint-context-DEBUG: 04:23:55.991: No driver found for USB device 0BDA:5401
(process:17493): libfprint-context-DEBUG: 04:23:55.992: No driver found for USB device 1D6B:0002
(process:17493): libfprint-context-DEBUG: 04:23:55.992: No driver found for USB device 1D6B:0003
(process:17493): libfprint-context-DEBUG: 04:23:55.992: No driver found for USB device 0624:0249
(process:17493): libfprint-context-DEBUG: 04:23:55.992: No driver found for USB device 0624:0248
(process:17493): libfprint-context-DEBUG: 04:23:55.992: No driver found for USB device 1D6B:0002
(process:17493): libfprint-context-DEBUG: 04:23:55.993: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-_a6mka5s/virtual-device-storage.socket
(process:17493): libfprint-context-DEBUG: 04:23:56.002: created
(process:17493): libfprint-device-DEBUG: 04:23:56.026: Device reported probe completion
(process:17493): libfprint-device-DEBUG: 04:23:56.027: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17493): libfprint-device-DEBUG: 04:23:56.027: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:17493): libfprint-virtual_device-DEBUG: 04:23:56.039: 38977935637389: ../libfprint/drivers/virtual-device.c:387
(process:17493): libfprint-virtual_device_connection-DEBUG: 04:23:56.041: 38977935638780: ../libfprint/drivers/virtual-device-listener.c:153
(process:17493): libfprint-device-DEBUG: 04:23:56.044: Device reported open completion
(process:17493): libfprint-device-DEBUG: 04:23:56.044: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17493): libfprint-device-DEBUG: 04:23:56.045: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17493): libfprint-virtual_device_connection-DEBUG: 04:23:56.052: Got a new connection!
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.054: Got instructions of length 20
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.055: Received command SET_ENROLL_STAGES 20
(process:17493): libfprint-virtual_device_connection-DEBUG: 04:23:56.058: Got a new connection!
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.067: Got instructions of length 19
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.068: Received command SET_ENROLL_STAGES 1
(process:17493): libfprint-virtual_device_connection-DEBUG: 04:23:56.072: Got a new connection!
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.073: Got instructions of length 19
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.074: Received command SET_ENROLL_STAGES 0
(process:17493): libfprint-virtual_device_connection-DEBUG: 04:23:56.089: Got a new connection!
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.091: Got instructions of length 5
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.091: Received command CONT
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.093: Processing command CONT
(process:17493): libfprint-device-DEBUG: 04:23:56.093: Device reported deletion completion
(process:17493): libfprint-device-DEBUG: 04:23:56.094: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17493): libfprint-device-DEBUG: 04:23:56.094: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17493): libfprint-virtual_device_connection-DEBUG: 04:23:56.096: Got a new connection!
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.098: Got instructions of length 16
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.106: Received command SET_KEEP_ALIVE 0
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.107: Keep alive toggled: 0
(process:17493): libfprint-virtual_device_connection-DEBUG: 04:23:56.109: Got a new connection!
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.110: Got instructions of length 19
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.111: Received command SET_ENROLL_STAGES 5
(process:17493): libfprint-device-DEBUG: 04:23:56.113: Device reported close completion
(process:17493): libfprint-device-DEBUG: 04:23:56.114: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17493): libfprint-device-DEBUG: 04:23:56.114: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17493): libfprint-virtual_device_storage-DEBUG: 04:23:56.117: 38977935715321: ../libfprint/drivers/virtual-device-storage.c:253
(process:17493): libfprint-virtual_device-DEBUG: 04:23:56.118: 38977935715829: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.214s
OK
==============================================================================
=================================== 51/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_close_error
start time: 04:23:55
duration: 0.82s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=118 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_close_error
----------------------------------- stdout -----------------------------------
(process:17513): libfprint-context-DEBUG: 04:23:56.501: Initializing FpContext (libfprint version 1.94.6)
(process:17513): libfprint-context-DEBUG: 04:23:56.531: No driver found for USB device 1D6B:0003
(process:17513): libfprint-context-DEBUG: 04:23:56.531: No driver found for USB device 0BDA:5401
(process:17513): libfprint-context-DEBUG: 04:23:56.532: No driver found for USB device 1D6B:0002
(process:17513): libfprint-context-DEBUG: 04:23:56.532: No driver found for USB device 1D6B:0003
(process:17513): libfprint-context-DEBUG: 04:23:56.532: No driver found for USB device 0624:0249
(process:17513): libfprint-context-DEBUG: 04:23:56.532: No driver found for USB device 0624:0248
(process:17513): libfprint-context-DEBUG: 04:23:56.532: No driver found for USB device 1D6B:0002
(process:17513): libfprint-context-DEBUG: 04:23:56.532: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-9u3xr9ca/virtual-device-storage.socket
(process:17513): libfprint-context-DEBUG: 04:23:56.534: created
(process:17513): libfprint-device-DEBUG: 04:23:56.545: Device reported probe completion
(process:17513): libfprint-device-DEBUG: 04:23:56.546: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17513): libfprint-device-DEBUG: 04:23:56.547: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:17513): libfprint-virtual_device-DEBUG: 04:23:56.550: 38977936148712: ../libfprint/drivers/virtual-device.c:387
(process:17513): libfprint-virtual_device_connection-DEBUG: 04:23:56.552: 38977936150344: ../libfprint/drivers/virtual-device-listener.c:153
(process:17513): libfprint-device-DEBUG: 04:23:56.555: Device reported open completion
(process:17513): libfprint-device-DEBUG: 04:23:56.556: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17513): libfprint-device-DEBUG: 04:23:56.557: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17513): libfprint-virtual_device_connection-DEBUG: 04:23:56.560: Got a new connection!
(process:17513): libfprint-virtual_device-DEBUG: 04:23:56.562: Got instructions of length 9
(process:17513): libfprint-virtual_device-DEBUG: 04:23:56.562: Received command SLEEP 100
(process:17513): libfprint-virtual_device_connection-DEBUG: 04:23:56.566: Got a new connection!
(process:17513): libfprint-virtual_device-DEBUG: 04:23:56.567: Got instructions of length 7
(process:17513): libfprint-virtual_device-DEBUG: 04:23:56.568: Received command ERROR 4
(process:17513): libfprint-virtual_device-DEBUG: 04:23:56.571: Processing command SLEEP 100
(process:17513): libfprint-virtual_device-DEBUG: 04:23:56.571: Sleeping 100ms
(process:17513): libfprint-virtual_device-DEBUG: 04:23:56.674: Sleeping completed
(process:17513): libfprint-virtual_device-DEBUG: 04:23:56.674: Processing command ERROR 4
(process:17513): libfprint-device-DEBUG: 04:23:56.675: Device reported close completion
(process:17513): libfprint-device-DEBUG: 04:23:56.676: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17513): libfprint-device-DEBUG: 04:23:56.676: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
----------------------------------------------------------------------
Ran 1 test in 0.199s
OK
(process:17513): libfprint-virtual_device_storage-DEBUG: 04:23:56.705: 38977936303703: ../libfprint/drivers/virtual-device-storage.c:253
(process:17513): libfprint-virtual_device-DEBUG: 04:23:56.706: 38977936304385: ../libfprint/drivers/virtual-device.c:752
==============================================================================
=================================== 52/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_clear_storage_error
start time: 04:23:55
duration: 1.13s
result: exit status 0
command: MALLOC_PERTURB_=215 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_clear_storage_error
----------------------------------- stdout -----------------------------------
(process:17510): libfprint-context-DEBUG: 04:23:56.342: Initializing FpContext (libfprint version 1.94.6)
(process:17510): libfprint-context-DEBUG: 04:23:56.374: No driver found for USB device 1D6B:0003
(process:17510): libfprint-context-DEBUG: 04:23:56.374: No driver found for USB device 0BDA:5401
(process:17510): libfprint-context-DEBUG: 04:23:56.375: No driver found for USB device 1D6B:0002
(process:17510): libfprint-context-DEBUG: 04:23:56.375: No driver found for USB device 1D6B:0003
(process:17510): libfprint-context-DEBUG: 04:23:56.375: No driver found for USB device 0624:0249
(process:17510): libfprint-context-DEBUG: 04:23:56.375: No driver found for USB device 0624:0248
(process:17510): libfprint-context-DEBUG: 04:23:56.375: No driver found for USB device 1D6B:0002
(process:17510): libfprint-context-DEBUG: 04:23:56.376: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-facli_dv/virtual-device-storage.socket
(process:17510): libfprint-context-DEBUG: 04:23:56.377: created
(process:17510): libfprint-device-DEBUG: 04:23:56.392: Device reported probe completion
(process:17510): libfprint-device-DEBUG: 04:23:56.393: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17510): libfprint-device-DEBUG: 04:23:56.393: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:17510): libfprint-virtual_device-DEBUG: 04:23:56.398: 38977935995852: ../libfprint/drivers/virtual-device.c:387
(process:17510): libfprint-virtual_device_connection-DEBUG: 04:23:56.399: 38977935997728: ../libfprint/drivers/virtual-device-listener.c:153
(process:17510): libfprint-device-DEBUG: 04:23:56.403: Device reported open completion
(process:17510): libfprint-device-DEBUG: 04:23:56.404: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17510): libfprint-device-DEBUG: 04:23:56.404: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17510): libfprint-virtual_device_connection-DEBUG: 04:23:56.408: Got a new connection!
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.410: Got instructions of length 9
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.411: Received command INSERT p1
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.414: Processing command INSERT p1
(process:17510): libfprint-device-DEBUG: 04:23:56.916: Device reported listing completion
(process:17510): libfprint-device-DEBUG: 04:23:56.917: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17510): libfprint-device-DEBUG: 04:23:56.917: Updated temperature model after 0.51 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17510): libfprint-virtual_device_connection-DEBUG: 04:23:56.920: Got a new connection!
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.921: Got instructions of length 7
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.921: Received command ERROR 5
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.922: Processing command ERROR 5
(process:17510): libfprint-device-DEBUG: 04:23:56.922: Device reported deletion completion
(process:17510): libfprint-device-DEBUG: 04:23:56.923: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17510): libfprint-device-DEBUG: 04:23:56.923: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17510): libfprint-virtual_device_connection-DEBUG: 04:23:56.925: Got a new connection!
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.926: Got instructions of length 5
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.926: Received command CONT
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.927: Processing command CONT
(process:17510): libfprint-device-DEBUG: 04:23:56.927: Device reported deletion completion
(process:17510): libfprint-device-DEBUG: 04:23:56.928: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17510): libfprint-device-DEBUG: 04:23:56.928: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17510): libfprint-virtual_device_connection-DEBUG: 04:23:56.929: Got a new connection!
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.946: Got instructions of length 16
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.947: Received command SET_KEEP_ALIVE 0
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.947: Keep alive toggled: 0
(process:17510): libfprint-virtual_device_connection-DEBUG: 04:23:56.949: Got a new connection!
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.950: Got instructions of length 19
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.950: Received command SET_ENROLL_STAGES 5
(process:17510): libfprint-device-DEBUG: 04:23:56.951: Device reported close completion
(process:17510): libfprint-device-DEBUG: 04:23:56.952: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17510): libfprint-device-DEBUG: 04:23:56.952: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
<FPrint.Print object at 0xf6e5cd08 (FpPrint at 0x12b1cc0)>
ok
(process:17510): libfprint-virtual_device_storage-DEBUG: 04:23:56.954: 38977936552051: ../libfprint/drivers/virtual-device-storage.c:253
(process:17510): libfprint-virtual_device-DEBUG: 04:23:56.954: 38977936552188: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.626s
OK
==============================================================================
=================================== 53/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_clear_storage
start time: 04:23:55
duration: 1.76s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests MALLOC_PERTURB_=197 FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_clear_storage
----------------------------------- stdout -----------------------------------
(process:17505): libfprint-context-DEBUG: 04:23:56.189: Initializing FpContext (libfprint version 1.94.6)
(process:17505): libfprint-context-DEBUG: 04:23:56.260: No driver found for USB device 1D6B:0003
(process:17505): libfprint-context-DEBUG: 04:23:56.261: No driver found for USB device 0BDA:5401
(process:17505): libfprint-context-DEBUG: 04:23:56.261: No driver found for USB device 1D6B:0002
(process:17505): libfprint-context-DEBUG: 04:23:56.261: No driver found for USB device 1D6B:0003
(process:17505): libfprint-context-DEBUG: 04:23:56.261: No driver found for USB device 0624:0249
(process:17505): libfprint-context-DEBUG: 04:23:56.261: No driver found for USB device 0624:0248
(process:17505): libfprint-context-DEBUG: 04:23:56.261: No driver found for USB device 1D6B:0002
(process:17505): libfprint-context-DEBUG: 04:23:56.262: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-t_xfsvw4/virtual-device-storage.socket
(process:17505): libfprint-context-DEBUG: 04:23:56.263: created
(process:17505): libfprint-device-DEBUG: 04:23:56.283: Device reported probe completion
(process:17505): libfprint-device-DEBUG: 04:23:56.283: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17505): libfprint-device-DEBUG: 04:23:56.284: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:17505): libfprint-virtual_device-DEBUG: 04:23:56.287: 38977935885007: ../libfprint/drivers/virtual-device.c:387
(process:17505): libfprint-virtual_device_connection-DEBUG: 04:23:56.288: 38977935886330: ../libfprint/drivers/virtual-device-listener.c:153
(process:17505): libfprint-device-DEBUG: 04:23:56.291: Device reported open completion
(process:17505): libfprint-device-DEBUG: 04:23:56.291: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17505): libfprint-device-DEBUG: 04:23:56.292: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17505): libfprint-virtual_device_connection-DEBUG: 04:23:56.294: Got a new connection!
(process:17505): libfprint-virtual_device-DEBUG: 04:23:56.296: Got instructions of length 9
(process:17505): libfprint-virtual_device-DEBUG: 04:23:56.296: Received command INSERT p1
(process:17505): libfprint-virtual_device-DEBUG: 04:23:56.315: Processing command INSERT p1
(process:17505): libfprint-device-DEBUG: 04:23:56.819: Device reported listing completion
(process:17505): libfprint-device-DEBUG: 04:23:56.820: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17505): libfprint-device-DEBUG: 04:23:56.820: Updated temperature model after 0.53 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17505): libfprint-virtual_device_connection-DEBUG: 04:23:56.821: Got a new connection!
(process:17505): libfprint-virtual_device-DEBUG: 04:23:56.823: Got instructions of length 5
(process:17505): libfprint-virtual_device-DEBUG: 04:23:56.824: Received command CONT
(process:17505): libfprint-virtual_device-DEBUG: 04:23:56.825: Processing command CONT
(process:17505): libfprint-device-DEBUG: 04:23:56.826: Device reported deletion completion
(process:17505): libfprint-device-DEBUG: 04:23:56.826: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17505): libfprint-device-DEBUG: 04:23:56.827: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17505): libfprint-device-DEBUG: 04:23:57.330: Device reported listing completion
(process:17505): libfprint-device-DEBUG: 04:23:57.331: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17505): libfprint-device-DEBUG: 04:23:57.331: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17505): libfprint-virtual_device_connection-DEBUG: 04:23:57.333: Got a new connection!
(process:17505): libfprint-virtual_device-DEBUG: 04:23:57.334: Got instructions of length 5
(process:17505): libfprint-virtual_device-DEBUG: 04:23:57.334: Received command CONT
(process:17505): libfprint-virtual_device-DEBUG: 04:23:57.335: Processing command CONT
(process:17505): libfprint-device-DEBUG: 04:23:57.335: Device reported deletion completion
(process:17505): libfprint-device-DEBUG: 04:23:57.335: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17505): libfprint-device-DEBUG: 04:23:57.336: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17505): libfprint-virtual_device_connection-DEBUG: 04:23:57.337: Got a new connection!
(process:17505): libfprint-virtual_device-DEBUG: 04:23:57.338: Got instructions of length 16
(process:17505): libfprint-virtual_device-DEBUG: 04:23:57.338: Received command SET_KEEP_ALIVE 0
(process:17505): libfprint-virtual_device-DEBUG: 04:23:57.338: Keep alive toggled: 0
(process:17505): libfprint-virtual_device_connection-DEBUG: 04:23:57.340: Got a new connection!
(process:17505): libfprint-virtual_device-DEBUG: 04:23:57.341: Got instructions of length 19
(process:17505): libfprint-virtual_device-DEBUG: 04:23:57.341: Received command SET_ENROLL_STAGES 5
(process:17505): libfprint-device-DEBUG: 04:23:57.351: Device reported close completion
(process:17505): libfprint-device-DEBUG: 04:23:57.352: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17505): libfprint-device-DEBUG: 04:23:57.352: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
<FPrint.Print object at 0xf6fe6a08 (FpPrint at 0x14c80c0)>
ok
(process:17505): libfprint-virtual_device_storage-DEBUG: 04:23:57.354: 38977936951815: ../libfprint/drivers/virtual-device-storage.c:253
(process:17505): libfprint-virtual_device-DEBUG: 04:23:57.354: 38977936951962: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 1.206s
OK
==============================================================================
=================================== 54/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_close_while_opening
start time: 04:23:56
duration: 1.32s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=57 FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_close_while_opening
----------------------------------- stdout -----------------------------------
(process:17518): libfprint-context-DEBUG: 04:23:56.836: Initializing FpContext (libfprint version 1.94.6)
(process:17518): libfprint-context-DEBUG: 04:23:56.870: No driver found for USB device 1D6B:0003
(process:17518): libfprint-context-DEBUG: 04:23:56.870: No driver found for USB device 0BDA:5401
(process:17518): libfprint-context-DEBUG: 04:23:56.870: No driver found for USB device 1D6B:0002
(process:17518): libfprint-context-DEBUG: 04:23:56.870: No driver found for USB device 1D6B:0003
(process:17518): libfprint-context-DEBUG: 04:23:56.870: No driver found for USB device 0624:0249
(process:17518): libfprint-context-DEBUG: 04:23:56.871: No driver found for USB device 0624:0248
(process:17518): libfprint-context-DEBUG: 04:23:56.871: No driver found for USB device 1D6B:0002
(process:17518): libfprint-context-DEBUG: 04:23:56.871: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-ve4vy_q1/virtual-device-storage.socket
(process:17518): libfprint-context-DEBUG: 04:23:56.872: created
(process:17518): libfprint-device-DEBUG: 04:23:56.884: Device reported probe completion
(process:17518): libfprint-device-DEBUG: 04:23:56.885: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17518): libfprint-device-DEBUG: 04:23:56.885: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_close_while_opening (__main__.VirtualDeviceStorage.test_close_while_opening) ... (process:17518): libfprint-virtual_device-DEBUG: 04:23:56.888: 38977936486324: ../libfprint/drivers/virtual-device.c:387
(process:17518): libfprint-virtual_device_connection-DEBUG: 04:23:56.889: 38977936487640: ../libfprint/drivers/virtual-device-listener.c:153
(process:17518): libfprint-device-DEBUG: 04:23:56.893: Device reported open completion
(process:17518): libfprint-device-DEBUG: 04:23:56.894: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17518): libfprint-device-DEBUG: 04:23:56.895: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17518): libfprint-virtual_device_connection-DEBUG: 04:23:56.898: Got a new connection!
(process:17518): libfprint-virtual_device-DEBUG: 04:23:56.900: Got instructions of length 16
(process:17518): libfprint-virtual_device-DEBUG: 04:23:56.900: Received command SET_KEEP_ALIVE 1
(process:17518): libfprint-virtual_device-DEBUG: 04:23:56.901: Keep alive toggled: 1
(process:17518): libfprint-device-DEBUG: 04:23:56.902: Device reported close completion
(process:17518): libfprint-device-DEBUG: 04:23:56.903: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17518): libfprint-device-DEBUG: 04:23:56.903: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17518): libfprint-virtual_device_connection-DEBUG: 04:23:56.905: Got a new connection!
(process:17518): libfprint-virtual_device-DEBUG: 04:23:56.907: Got instructions of length 9
(process:17518): libfprint-virtual_device-DEBUG: 04:23:56.907: Received command SLEEP 500
(process:17518): libfprint-virtual_device-DEBUG: 04:23:56.910: 38977936508474: ../libfprint/drivers/virtual-device.c:387
(process:17518): libfprint-virtual_device-DEBUG: 04:23:56.911: Processing command SLEEP 500
(process:17518): libfprint-virtual_device-DEBUG: 04:23:56.911: Sleeping 500ms
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.414: Sleeping completed
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.414: 38977937012331: ../libfprint/drivers/virtual-device.c:387
(process:17518): libfprint-device-DEBUG: 04:23:57.414: Device reported open completion
(process:17518): libfprint-device-DEBUG: 04:23:57.415: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17518): libfprint-device-DEBUG: 04:23:57.415: Updated temperature model after 0.51 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17518): libfprint-virtual_device_connection-DEBUG: 04:23:57.418: Got a new connection!
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.419: Got instructions of length 5
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.419: Received command CONT
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.420: Processing command CONT
(process:17518): libfprint-device-DEBUG: 04:23:57.421: Device reported deletion completion
(process:17518): libfprint-device-DEBUG: 04:23:57.421: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17518): libfprint-device-DEBUG: 04:23:57.421: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17518): libfprint-virtual_device_connection-DEBUG: 04:23:57.431: Got a new connection!
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.432: Got instructions of length 16
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.432: Received command SET_KEEP_ALIVE 0
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.432: Keep alive toggled: 0
(process:17518): libfprint-virtual_device_connection-DEBUG: 04:23:57.434: Got a new connection!
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.435: Got instructions of length 19
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.435: Received command SET_ENROLL_STAGES 5
(process:17518): libfprint-device-DEBUG: 04:23:57.436: Device reported close completion
(process:17518): libfprint-device-DEBUG: 04:23:57.436: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17518): libfprint-device-DEBUG: 04:23:57.437: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17518): libfprint-virtual_device_storage-DEBUG: 04:23:57.447: 38977937044742: ../libfprint/drivers/virtual-device-storage.c:253
(process:17518): libfprint-virtual_device-DEBUG: 04:23:57.449: 38977937045378: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.628s
OK
==============================================================================
=================================== 55/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_delayed_open
start time: 04:23:56
duration: 1.18s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=118 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_delayed_open
----------------------------------- stdout -----------------------------------
(process:17528): libfprint-context-DEBUG: 04:23:57.239: Initializing FpContext (libfprint version 1.94.6)
(process:17528): libfprint-context-DEBUG: 04:23:57.271: No driver found for USB device 1D6B:0003
(process:17528): libfprint-context-DEBUG: 04:23:57.272: No driver found for USB device 0BDA:5401
(process:17528): libfprint-context-DEBUG: 04:23:57.272: No driver found for USB device 1D6B:0002
(process:17528): libfprint-context-DEBUG: 04:23:57.273: No driver found for USB device 1D6B:0003
(process:17528): libfprint-context-DEBUG: 04:23:57.273: No driver found for USB device 0624:0249
(process:17528): libfprint-context-DEBUG: 04:23:57.273: No driver found for USB device 0624:0248
(process:17528): libfprint-context-DEBUG: 04:23:57.274: No driver found for USB device 1D6B:0002
(process:17528): libfprint-context-DEBUG: 04:23:57.274: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-ne0c4dxk/virtual-device-storage.socket
(process:17528): libfprint-context-DEBUG: 04:23:57.276: created
(process:17528): libfprint-device-DEBUG: 04:23:57.289: Device reported probe completion
(process:17528): libfprint-device-DEBUG: 04:23:57.291: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17528): libfprint-device-DEBUG: 04:23:57.292: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_delayed_open (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:17528): libfprint-virtual_device-DEBUG: 04:23:57.296: 38977936894252: ../libfprint/drivers/virtual-device.c:387
(process:17528): libfprint-virtual_device_connection-DEBUG: 04:23:57.298: 38977936896025: ../libfprint/drivers/virtual-device-listener.c:153
(process:17528): libfprint-device-DEBUG: 04:23:57.301: Device reported open completion
(process:17528): libfprint-device-DEBUG: 04:23:57.302: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17528): libfprint-device-DEBUG: 04:23:57.303: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17528): libfprint-virtual_device_connection-DEBUG: 04:23:57.306: Got a new connection!
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.308: Got instructions of length 16
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.308: Received command IGNORED_COMMAND
(process:17528): libfprint-virtual_device_connection-DEBUG: 04:23:57.311: Got a new connection!
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.312: Got instructions of length 9
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.313: Received command SLEEP 500
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.316: Processing command IGNORED_COMMAND
(process:17528): libfprint-device-DEBUG: 04:23:57.317: Device reported close completion
(process:17528): libfprint-device-DEBUG: 04:23:57.318: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17528): libfprint-device-DEBUG: 04:23:57.318: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.326: 38977936924462: ../libfprint/drivers/virtual-device.c:387
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.327: Processing command SLEEP 500
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.327: Sleeping 500ms
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.830: Sleeping completed
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.830: 38977937428269: ../libfprint/drivers/virtual-device.c:387
(process:17528): libfprint-virtual_device_connection-DEBUG: 04:23:57.830: 38977937428528: ../libfprint/drivers/virtual-device-listener.c:153
(process:17528): libfprint-device-DEBUG: 04:23:57.832: Device reported open completion
(process:17528): libfprint-device-DEBUG: 04:23:57.832: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17528): libfprint-device-DEBUG: 04:23:57.832: Updated temperature model after 0.51 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17528): libfprint-virtual_device_connection-DEBUG: 04:23:57.835: Got a new connection!
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.836: Got instructions of length 5
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.837: Received command CONT
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.838: Processing command CONT
(process:17528): libfprint-device-DEBUG: 04:23:57.838: Device reported deletion completion
(process:17528): libfprint-device-DEBUG: 04:23:57.838: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17528): libfprint-device-DEBUG: 04:23:57.839: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17528): libfprint-virtual_device_connection-DEBUG: 04:23:57.840: Got a new connection!
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.841: Got instructions of length 16
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.841: Received command SET_KEEP_ALIVE 0
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.841: Keep alive toggled: 0
(process:17528): libfprint-virtual_device_connection-DEBUG: 04:23:57.847: Got a new connection!
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.848: Got instructions of length 19
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.848: Received command SET_ENROLL_STAGES 5
(process:17528): libfprint-device-DEBUG: 04:23:57.850: Device reported close completion
(process:17528): libfprint-device-DEBUG: 04:23:57.850: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17528): libfprint-device-DEBUG: 04:23:57.850: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17528): libfprint-virtual_device_storage-DEBUG: 04:23:57.852: 38977937450480: ../libfprint/drivers/virtual-device-storage.c:253
(process:17528): libfprint-virtual_device-DEBUG: 04:23:57.852: 38977937450642: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.628s
OK
==============================================================================
=================================== 56/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_delayed_open_with_keep_alive
start time: 04:23:57
duration: 1.08s
result: exit status 0
command: G_DEBUG=fatal-warnings MALLOC_PERTURB_=206 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_delayed_open_with_keep_alive
----------------------------------- stdout -----------------------------------
(process:17533): libfprint-context-DEBUG: 04:23:57.428: Initializing FpContext (libfprint version 1.94.6)
(process:17533): libfprint-context-DEBUG: 04:23:57.459: No driver found for USB device 1D6B:0003
(process:17533): libfprint-context-DEBUG: 04:23:57.460: No driver found for USB device 0BDA:5401
(process:17533): libfprint-context-DEBUG: 04:23:57.460: No driver found for USB device 1D6B:0002
(process:17533): libfprint-context-DEBUG: 04:23:57.460: No driver found for USB device 1D6B:0003
(process:17533): libfprint-context-DEBUG: 04:23:57.460: No driver found for USB device 0624:0249
(process:17533): libfprint-context-DEBUG: 04:23:57.460: No driver found for USB device 0624:0248
(process:17533): libfprint-context-DEBUG: 04:23:57.460: No driver found for USB device 1D6B:0002
(process:17533): libfprint-context-DEBUG: 04:23:57.461: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-767z0hds/virtual-device-storage.socket
(process:17533): libfprint-context-DEBUG: 04:23:57.462: created
(process:17533): libfprint-device-DEBUG: 04:23:57.473: Device reported probe completion
(process:17533): libfprint-device-DEBUG: 04:23:57.474: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17533): libfprint-device-DEBUG: 04:23:57.474: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_delayed_open_with_keep_alive (__main__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:17533): libfprint-virtual_device-DEBUG: 04:23:57.477: 38977937075657: ../libfprint/drivers/virtual-device.c:387
(process:17533): libfprint-virtual_device_connection-DEBUG: 04:23:57.479: 38977937077017: ../libfprint/drivers/virtual-device-listener.c:153
(process:17533): libfprint-device-DEBUG: 04:23:57.482: Device reported open completion
(process:17533): libfprint-device-DEBUG: 04:23:57.482: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17533): libfprint-device-DEBUG: 04:23:57.482: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17533): libfprint-virtual_device_connection-DEBUG: 04:23:57.485: Got a new connection!
(process:17533): libfprint-virtual_device-DEBUG: 04:23:57.492: Got instructions of length 16
(process:17533): libfprint-virtual_device-DEBUG: 04:23:57.492: Received command SET_KEEP_ALIVE 1
(process:17533): libfprint-virtual_device-DEBUG: 04:23:57.493: Keep alive toggled: 1
(process:17533): libfprint-device-DEBUG: 04:23:57.494: Device reported close completion
(process:17533): libfprint-device-DEBUG: 04:23:57.494: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17533): libfprint-device-DEBUG: 04:23:57.494: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17533): libfprint-virtual_device_connection-DEBUG: 04:23:57.496: Got a new connection!
(process:17533): libfprint-virtual_device-DEBUG: 04:23:57.497: Got instructions of length 9
(process:17533): libfprint-virtual_device-DEBUG: 04:23:57.497: Received command SLEEP 500
(process:17533): libfprint-virtual_device-DEBUG: 04:23:57.501: 38977937099505: ../libfprint/drivers/virtual-device.c:387
(process:17533): libfprint-virtual_device-DEBUG: 04:23:57.501: Processing command SLEEP 500
(process:17533): libfprint-virtual_device-DEBUG: 04:23:57.502: Sleeping 500ms
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.007: Sleeping completed
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.007: 38977937605682: ../libfprint/drivers/virtual-device.c:387
(process:17533): libfprint-device-DEBUG: 04:23:58.008: Device reported open completion
(process:17533): libfprint-device-DEBUG: 04:23:58.008: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17533): libfprint-device-DEBUG: 04:23:58.008: Updated temperature model after 0.51 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17533): libfprint-virtual_device_connection-DEBUG: 04:23:58.011: Got a new connection!
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.012: Got instructions of length 5
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.012: Received command CONT
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.014: Processing command CONT
(process:17533): libfprint-device-DEBUG: 04:23:58.014: Device reported deletion completion
(process:17533): libfprint-device-DEBUG: 04:23:58.014: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17533): libfprint-device-DEBUG: 04:23:58.014: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17533): libfprint-virtual_device_connection-DEBUG: 04:23:58.016: Got a new connection!
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.017: Got instructions of length 16
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.017: Received command SET_KEEP_ALIVE 0
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.017: Keep alive toggled: 0
(process:17533): libfprint-virtual_device_connection-DEBUG: 04:23:58.027: Got a new connection!
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.028: Got instructions of length 19
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.028: Received command SET_ENROLL_STAGES 5
(process:17533): libfprint-device-DEBUG: 04:23:58.029: Device reported close completion
(process:17533): libfprint-device-DEBUG: 04:23:58.034: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17533): libfprint-device-DEBUG: 04:23:58.034: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17533): libfprint-virtual_device_storage-DEBUG: 04:23:58.036: 38977937634003: ../libfprint/drivers/virtual-device-storage.c:253
(process:17533): libfprint-virtual_device-DEBUG: 04:23:58.036: 38977937634144: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.631s
OK
==============================================================================
=================================== 57/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_delete_error
start time: 04:23:57
duration: 0.89s
result: exit status 0
command: G_DEBUG=fatal-warnings MALLOC_PERTURB_=4 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_delete_error
----------------------------------- stdout -----------------------------------
(process:17541): libfprint-context-DEBUG: 04:23:57.979: Initializing FpContext (libfprint version 1.94.6)
(process:17541): libfprint-context-DEBUG: 04:23:58.048: No driver found for USB device 1D6B:0003
(process:17541): libfprint-context-DEBUG: 04:23:58.048: No driver found for USB device 0BDA:5401
(process:17541): libfprint-context-DEBUG: 04:23:58.048: No driver found for USB device 1D6B:0002
(process:17541): libfprint-context-DEBUG: 04:23:58.049: No driver found for USB device 1D6B:0003
(process:17541): libfprint-context-DEBUG: 04:23:58.049: No driver found for USB device 0624:0249
(process:17541): libfprint-context-DEBUG: 04:23:58.049: No driver found for USB device 0624:0248
(process:17541): libfprint-context-DEBUG: 04:23:58.049: No driver found for USB device 1D6B:0002
(process:17541): libfprint-context-DEBUG: 04:23:58.049: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-jcewi51h/virtual-device-storage.socket
(process:17541): libfprint-context-DEBUG: 04:23:58.051: created
(process:17541): libfprint-device-DEBUG: 04:23:58.079: Device reported probe completion
(process:17541): libfprint-device-DEBUG: 04:23:58.079: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17541): libfprint-device-DEBUG: 04:23:58.080: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:17541): libfprint-virtual_device-DEBUG: 04:23:58.091: 38977937689509: ../libfprint/drivers/virtual-device.c:387
(process:17541): libfprint-virtual_device_connection-DEBUG: 04:23:58.093: 38977937690913: ../libfprint/drivers/virtual-device-listener.c:153
(process:17541): libfprint-device-DEBUG: 04:23:58.096: Device reported open completion
(process:17541): libfprint-device-DEBUG: 04:23:58.096: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17541): libfprint-device-DEBUG: 04:23:58.096: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17541): libfprint-virtual_device_connection-DEBUG: 04:23:58.107: Got a new connection!
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.109: Got instructions of length 9
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.109: Received command SLEEP 100
(process:17541): libfprint-virtual_device_connection-DEBUG: 04:23:58.112: Got a new connection!
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.113: Got instructions of length 7
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.114: Received command ERROR 7
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.127: Processing command SLEEP 100
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.128: Sleeping 100ms
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.230: Sleeping completed
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.230: Processing command ERROR 7
(process:17541): libfprint-device-DEBUG: 04:23:58.230: Device reported deletion completion
(process:17541): libfprint-device-DEBUG: 04:23:58.231: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(process:17541): libfprint-device-DEBUG: 04:23:58.231: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17541): libfprint-virtual_device_connection-DEBUG: 04:23:58.234: Got a new connection!
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.235: Got instructions of length 5
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.235: Received command CONT
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.237: Processing command CONT
(process:17541): libfprint-device-DEBUG: 04:23:58.237: Device reported deletion completion
(process:17541): libfprint-device-DEBUG: 04:23:58.237: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17541): libfprint-device-DEBUG: 04:23:58.237: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17541): libfprint-virtual_device_connection-DEBUG: 04:23:58.243: Got a new connection!
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.244: Got instructions of length 16
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.244: Received command SET_KEEP_ALIVE 0
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.244: Keep alive toggled: 0
(process:17541): libfprint-virtual_device_connection-DEBUG: 04:23:58.246: Got a new connection!
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.251: Got instructions of length 19
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.251: Received command SET_ENROLL_STAGES 5
(process:17541): libfprint-device-DEBUG: 04:23:58.253: Device reported close completion
(process:17541): libfprint-device-DEBUG: 04:23:58.253: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17541): libfprint-device-DEBUG: 04:23:58.253: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
----------------------------------------------------------------------
Ran 1 test in 0.305s
OK
(process:17541): libfprint-virtual_device_storage-DEBUG: 04:23:58.289: 38977937886973: ../libfprint/drivers/virtual-device-storage.c:253
(process:17541): libfprint-virtual_device-DEBUG: 04:23:58.289: 38977937887191: ../libfprint/drivers/virtual-device.c:752
==============================================================================
=================================== 58/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_device_features
start time: 04:23:57
duration: 0.65s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=210 FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_device_features
----------------------------------- stdout -----------------------------------
(process:17546): libfprint-context-DEBUG: 04:23:58.434: Initializing FpContext (libfprint version 1.94.6)
(process:17546): libfprint-context-DEBUG: 04:23:58.464: No driver found for USB device 1D6B:0003
(process:17546): libfprint-context-DEBUG: 04:23:58.465: No driver found for USB device 0BDA:5401
(process:17546): libfprint-context-DEBUG: 04:23:58.465: No driver found for USB device 1D6B:0002
(process:17546): libfprint-context-DEBUG: 04:23:58.466: No driver found for USB device 1D6B:0003
(process:17546): libfprint-context-DEBUG: 04:23:58.466: No driver found for USB device 0624:0249
(process:17546): libfprint-context-DEBUG: 04:23:58.467: No driver found for USB device 0624:0248
(process:17546): libfprint-context-DEBUG: 04:23:58.467: No driver found for USB device 1D6B:0002
(process:17546): libfprint-context-DEBUG: 04:23:58.468: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-_f8_6huw/virtual-device-storage.socket
(process:17546): libfprint-context-DEBUG: 04:23:58.469: created
(process:17546): libfprint-device-DEBUG: 04:23:58.480: Device reported probe completion
(process:17546): libfprint-device-DEBUG: 04:23:58.481: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17546): libfprint-device-DEBUG: 04:23:58.482: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:17546): libfprint-virtual_device-DEBUG: 04:23:58.486: 38977938083887: ../libfprint/drivers/virtual-device.c:387
(process:17546): libfprint-virtual_device_connection-DEBUG: 04:23:58.487: 38977938085543: ../libfprint/drivers/virtual-device-listener.c:153
(process:17546): libfprint-device-DEBUG: 04:23:58.491: Device reported open completion
(process:17546): libfprint-device-DEBUG: 04:23:58.491: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17546): libfprint-device-DEBUG: 04:23:58.492: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17546): libfprint-virtual_device_connection-DEBUG: 04:23:58.496: Got a new connection!
(process:17546): libfprint-virtual_device-DEBUG: 04:23:58.498: Got instructions of length 5
(process:17546): libfprint-virtual_device-DEBUG: 04:23:58.499: Received command CONT
(process:17546): libfprint-virtual_device-DEBUG: 04:23:58.500: Processing command CONT
(process:17546): libfprint-device-DEBUG: 04:23:58.501: Device reported deletion completion
(process:17546): libfprint-device-DEBUG: 04:23:58.501: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17546): libfprint-device-DEBUG: 04:23:58.502: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17546): libfprint-virtual_device_connection-DEBUG: 04:23:58.505: Got a new connection!
(process:17546): libfprint-virtual_device-DEBUG: 04:23:58.507: Got instructions of length 16
(process:17546): libfprint-virtual_device-DEBUG: 04:23:58.507: Received command SET_KEEP_ALIVE 0
(process:17546): libfprint-virtual_device-DEBUG: 04:23:58.507: Keep alive toggled: 0
(process:17546): libfprint-virtual_device_connection-DEBUG: 04:23:58.510: Got a new connection!
(process:17546): libfprint-virtual_device-DEBUG: 04:23:58.511: Got instructions of length 19
(process:17546): libfprint-virtual_device-DEBUG: 04:23:58.511: Received command SET_ENROLL_STAGES 5
(process:17546): libfprint-device-DEBUG: 04:23:58.513: Device reported close completion
(process:17546): libfprint-device-DEBUG: 04:23:58.514: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17546): libfprint-device-DEBUG: 04:23:58.515: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17546): libfprint-virtual_device_storage-DEBUG: 04:23:58.517: 38977938115131: ../libfprint/drivers/virtual-device-storage.c:253
(process:17546): libfprint-virtual_device-DEBUG: 04:23:58.517: 38977938115594: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.103s
OK
==============================================================================
=================================== 59/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_device_properties
start time: 04:23:58
duration: 0.52s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MALLOC_PERTURB_=248 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_device_properties
----------------------------------- stdout -----------------------------------
(process:17553): libfprint-context-DEBUG: 04:23:58.503: Initializing FpContext (libfprint version 1.94.6)
(process:17553): libfprint-context-DEBUG: 04:23:58.535: No driver found for USB device 1D6B:0003
(process:17553): libfprint-context-DEBUG: 04:23:58.535: No driver found for USB device 0BDA:5401
(process:17553): libfprint-context-DEBUG: 04:23:58.535: No driver found for USB device 1D6B:0002
(process:17553): libfprint-context-DEBUG: 04:23:58.535: No driver found for USB device 1D6B:0003
(process:17553): libfprint-context-DEBUG: 04:23:58.535: No driver found for USB device 0624:0249
(process:17553): libfprint-context-DEBUG: 04:23:58.535: No driver found for USB device 0624:0248
(process:17553): libfprint-context-DEBUG: 04:23:58.536: No driver found for USB device 1D6B:0002
(process:17553): libfprint-context-DEBUG: 04:23:58.536: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-641ilv4z/virtual-device-storage.socket
(process:17553): libfprint-context-DEBUG: 04:23:58.537: created
(process:17553): libfprint-device-DEBUG: 04:23:58.549: Device reported probe completion
(process:17553): libfprint-device-DEBUG: 04:23:58.550: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17553): libfprint-device-DEBUG: 04:23:58.550: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:17553): libfprint-virtual_device-DEBUG: 04:23:58.553: 38977938151339: ../libfprint/drivers/virtual-device.c:387
(process:17553): libfprint-virtual_device_connection-DEBUG: 04:23:58.554: 38977938152672: ../libfprint/drivers/virtual-device-listener.c:153
(process:17553): libfprint-device-DEBUG: 04:23:58.557: Device reported open completion
(process:17553): libfprint-device-DEBUG: 04:23:58.558: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17553): libfprint-device-DEBUG: 04:23:58.558: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17553): libfprint-virtual_device_connection-DEBUG: 04:23:58.565: Got a new connection!
(process:17553): libfprint-virtual_device-DEBUG: 04:23:58.567: Got instructions of length 5
(process:17553): libfprint-virtual_device-DEBUG: 04:23:58.567: Received command CONT
(process:17553): libfprint-virtual_device-DEBUG: 04:23:58.568: Processing command CONT
(process:17553): libfprint-device-DEBUG: 04:23:58.568: Device reported deletion completion
(process:17553): libfprint-device-DEBUG: 04:23:58.568: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17553): libfprint-device-DEBUG: 04:23:58.569: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17553): libfprint-virtual_device_connection-DEBUG: 04:23:58.570: Got a new connection!
(process:17553): libfprint-virtual_device-DEBUG: 04:23:58.571: Got instructions of length 16
(process:17553): libfprint-virtual_device-DEBUG: 04:23:58.572: Received command SET_KEEP_ALIVE 0
(process:17553): libfprint-virtual_device-DEBUG: 04:23:58.572: Keep alive toggled: 0
(process:17553): libfprint-virtual_device_connection-DEBUG: 04:23:58.573: Got a new connection!
(process:17553): libfprint-virtual_device-DEBUG: 04:23:58.574: Got instructions of length 19
(process:17553): libfprint-virtual_device-DEBUG: 04:23:58.575: Received command SET_ENROLL_STAGES 5
(process:17553): libfprint-device-DEBUG: 04:23:58.576: Device reported close completion
(process:17553): libfprint-device-DEBUG: 04:23:58.576: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17553): libfprint-device-DEBUG: 04:23:58.577: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17553): libfprint-virtual_device_storage-DEBUG: 04:23:58.578: 38977938176683: ../libfprint/drivers/virtual-device-storage.c:253
(process:17553): libfprint-virtual_device-DEBUG: 04:23:58.579: 38977938176827: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.096s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:1067: DeprecationWarning: FPrint.Device.supports_identify is deprecated
self.assertTrue(self.dev.supports_identify())
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:1068: DeprecationWarning: FPrint.Device.supports_capture is deprecated
self.assertFalse(self.dev.supports_capture())
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:1069: DeprecationWarning: FPrint.Device.has_storage is deprecated
self.assertTrue(self.dev.has_storage())
==============================================================================
=================================== 60/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_delete_multiple_times
start time: 04:23:57
duration: 1.73s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=207 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_delete_multiple_times
----------------------------------- stdout -----------------------------------
(process:17543): libfprint-context-DEBUG: 04:23:57.938: Initializing FpContext (libfprint version 1.94.6)
(process:17543): libfprint-context-DEBUG: 04:23:57.985: No driver found for USB device 1D6B:0003
(process:17543): libfprint-context-DEBUG: 04:23:57.985: No driver found for USB device 0BDA:5401
(process:17543): libfprint-context-DEBUG: 04:23:57.986: No driver found for USB device 1D6B:0002
(process:17543): libfprint-context-DEBUG: 04:23:57.986: No driver found for USB device 1D6B:0003
(process:17543): libfprint-context-DEBUG: 04:23:57.986: No driver found for USB device 0624:0249
(process:17543): libfprint-context-DEBUG: 04:23:57.986: No driver found for USB device 0624:0248
(process:17543): libfprint-context-DEBUG: 04:23:57.986: No driver found for USB device 1D6B:0002
(process:17543): libfprint-context-DEBUG: 04:23:57.986: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-a8n4tw8y/virtual-device-storage.socket
(process:17543): libfprint-context-DEBUG: 04:23:57.988: created
(process:17543): libfprint-device-DEBUG: 04:23:57.999: Device reported probe completion
(process:17543): libfprint-device-DEBUG: 04:23:57.999: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17543): libfprint-device-DEBUG: 04:23:58.000: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:17543): libfprint-virtual_device-DEBUG: 04:23:58.003: 38977937601165: ../libfprint/drivers/virtual-device.c:387
(process:17543): libfprint-virtual_device_connection-DEBUG: 04:23:58.004: 38977937602522: ../libfprint/drivers/virtual-device-listener.c:153
(process:17543): libfprint-device-DEBUG: 04:23:58.007: Device reported open completion
(process:17543): libfprint-device-DEBUG: 04:23:58.019: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17543): libfprint-device-DEBUG: 04:23:58.019: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17543): libfprint-virtual_device_connection-DEBUG: 04:23:58.032: Got a new connection!
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.036: Got instructions of length 16
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.037: Received command SCAN right-thumb
(process:17543): libfprint-device-DEBUG: 04:23:58.044: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.066: Processing command SCAN right-thumb
(process:17543): libfprint-device-DEBUG: 04:23:58.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17543): libfprint-device-DEBUG: 04:23:58.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17543): libfprint-device-DEBUG: 04:23:58.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17543): libfprint-device-DEBUG: 04:23:58.068: Device reported enroll progress, reported 1 of 5 have been completed
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.070: Sleeping completed
(process:17543): libfprint-virtual_device_connection-DEBUG: 04:23:58.071: Got a new connection!
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.073: Got instructions of length 16
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.073: Received command SCAN right-thumb
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.074: Processing command SCAN right-thumb
(process:17543): libfprint-device-DEBUG: 04:23:58.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17543): libfprint-device-DEBUG: 04:23:58.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17543): libfprint-device-DEBUG: 04:23:58.075: Device reported enroll progress, reported 2 of 5 have been completed
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.076: Sleeping completed
(process:17543): libfprint-virtual_device_connection-DEBUG: 04:23:58.078: Got a new connection!
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.081: Got instructions of length 16
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.081: Received command SCAN right-thumb
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.081: Processing command SCAN right-thumb
(process:17543): libfprint-device-DEBUG: 04:23:58.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17543): libfprint-device-DEBUG: 04:23:58.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17543): libfprint-device-DEBUG: 04:23:58.083: Device reported enroll progress, reported 3 of 5 have been completed
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.084: Sleeping completed
(process:17543): libfprint-virtual_device_connection-DEBUG: 04:23:58.086: Got a new connection!
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.093: Got instructions of length 16
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.094: Received command SCAN right-thumb
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.094: Processing command SCAN right-thumb
(process:17543): libfprint-device-DEBUG: 04:23:58.094: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17543): libfprint-device-DEBUG: 04:23:58.095: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17543): libfprint-device-DEBUG: 04:23:58.095: Device reported enroll progress, reported 4 of 5 have been completed
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.097: Sleeping completed
(process:17543): libfprint-virtual_device_connection-DEBUG: 04:23:58.100: Got a new connection!
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.107: Got instructions of length 16
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.108: Received command SCAN right-thumb
(process:17543): libfprint-virtual_device-DEBUG: 04:23:58.108: Processing command SCAN right-thumb
(process:17543): libfprint-device-DEBUG: 04:23:58.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17543): libfprint-device-DEBUG: 04:23:58.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17543): libfprint-device-DEBUG: 04:23:58.110: Device reported enroll progress, reported 5 of 5 have been completed
(process:17543): libfprint-device-DEBUG: 04:23:58.110: Device reported enroll completion
(process:17543): libfprint-device-DEBUG: 04:23:58.111: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17543): libfprint-device-DEBUG: 04:23:58.111: Print for finger FP_FINGER_RIGHT_THUMB enrolled
(process:17543): libfprint-device-DEBUG: 04:23:58.113: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17543): libfprint-device-DEBUG: 04:23:58.114: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17543): libfprint-virtual_device_storage-DEBUG: 04:23:58.622: Deleting print right-thumb for user testuser
(process:17543): libfprint-device-DEBUG: 04:23:58.622: Device reported deletion completion
(process:17543): libfprint-device-DEBUG: 04:23:58.622: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(process:17543): libfprint-device-DEBUG: 04:23:58.622: Updated temperature model after 0.51 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17543): libfprint-device-DEBUG: 04:23:58.734: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
(process:17543): libfprint-virtual_device_storage-DEBUG: 04:23:59.130: Deleting print right-thumb for user testuser
(process:17543): libfprint-device-DEBUG: 04:23:59.130: Device reported deletion completion
(process:17543): libfprint-device-DEBUG: 04:23:59.131: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(process:17543): libfprint-device-DEBUG: 04:23:59.131: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17543): libfprint-virtual_device_connection-DEBUG: 04:23:59.134: Got a new connection!
(process:17543): libfprint-virtual_device-DEBUG: 04:23:59.135: Got instructions of length 5
(process:17543): libfprint-virtual_device-DEBUG: 04:23:59.135: Received command CONT
(process:17543): libfprint-virtual_device-DEBUG: 04:23:59.137: Processing command CONT
(process:17543): libfprint-device-DEBUG: 04:23:59.137: Device reported deletion completion
(process:17543): libfprint-device-DEBUG: 04:23:59.137: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17543): libfprint-device-DEBUG: 04:23:59.137: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17543): libfprint-virtual_device_connection-DEBUG: 04:23:59.139: Got a new connection!
(process:17543): libfprint-virtual_device-DEBUG: 04:23:59.140: Got instructions of length 16
(process:17543): libfprint-virtual_device-DEBUG: 04:23:59.141: Received command SET_KEEP_ALIVE 0
(process:17543): libfprint-virtual_device-DEBUG: 04:23:59.141: Keep alive toggled: 0
(process:17543): libfprint-virtual_device_connection-DEBUG: 04:23:59.143: Got a new connection!
(process:17543): libfprint-virtual_device-DEBUG: 04:23:59.145: Got instructions of length 19
(process:17543): libfprint-virtual_device-DEBUG: 04:23:59.154: Received command SET_ENROLL_STAGES 5
(process:17543): libfprint-device-DEBUG: 04:23:59.156: Device reported close completion
(process:17543): libfprint-device-DEBUG: 04:23:59.157: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17543): libfprint-device-DEBUG: 04:23:59.158: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
Enroll done
ok
(process:17543): libfprint-virtual_device_storage-DEBUG: 04:23:59.160: 38977938758690: ../libfprint/drivers/virtual-device-storage.c:253
(process:17543): libfprint-virtual_device-DEBUG: 04:23:59.161: 38977938759180: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 1.246s
OK
==============================================================================
=================================== 61/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_device_sleep
start time: 04:23:58
duration: 1.30s
result: exit status 0
command: G_DEBUG=fatal-warnings MALLOC_PERTURB_=209 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_device_sleep
----------------------------------- stdout -----------------------------------
(process:17555): libfprint-context-DEBUG: 04:23:58.955: Initializing FpContext (libfprint version 1.94.6)
(process:17555): libfprint-context-DEBUG: 04:23:58.999: No driver found for USB device 1D6B:0003
(process:17555): libfprint-context-DEBUG: 04:23:58.999: No driver found for USB device 0BDA:5401
(process:17555): libfprint-context-DEBUG: 04:23:59.000: No driver found for USB device 1D6B:0002
(process:17555): libfprint-context-DEBUG: 04:23:59.000: No driver found for USB device 1D6B:0003
(process:17555): libfprint-context-DEBUG: 04:23:59.000: No driver found for USB device 0624:0249
(process:17555): libfprint-context-DEBUG: 04:23:59.000: No driver found for USB device 0624:0248
(process:17555): libfprint-context-DEBUG: 04:23:59.000: No driver found for USB device 1D6B:0002
(process:17555): libfprint-context-DEBUG: 04:23:59.000: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-q6hwps8h/virtual-device-storage.socket
(process:17555): libfprint-context-DEBUG: 04:23:59.010: created
(process:17555): libfprint-device-DEBUG: 04:23:59.032: Device reported probe completion
(process:17555): libfprint-device-DEBUG: 04:23:59.033: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17555): libfprint-device-DEBUG: 04:23:59.033: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:17555): libfprint-virtual_device-DEBUG: 04:23:59.040: 38977938638243: ../libfprint/drivers/virtual-device.c:387
(process:17555): libfprint-virtual_device_connection-DEBUG: 04:23:59.041: 38977938639651: ../libfprint/drivers/virtual-device-listener.c:153
(process:17555): libfprint-device-DEBUG: 04:23:59.049: Device reported open completion
(process:17555): libfprint-device-DEBUG: 04:23:59.049: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17555): libfprint-device-DEBUG: 04:23:59.049: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17555): libfprint-virtual_device_connection-DEBUG: 04:23:59.057: Got a new connection!
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.063: Got instructions of length 10
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.063: Received command SLEEP 1500
(process:17555): libfprint-device-DEBUG: 04:23:59.079: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.079: Processing command SLEEP 1500
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.079: Sleeping 1500ms
(process:17555): libfprint-device-DEBUG: 04:23:59.188: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17555): libfprint-device-DEBUG: 04:23:59.381: Idle cancelling on ongoing operation!
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.381: Got cancellation!
(process:17555): libfprint-device-DEBUG: 04:23:59.381: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17555): libfprint-device-DEBUG: 04:23:59.382: Device reported identify completion
(process:17555): libfprint-device-DEBUG: 04:23:59.382: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17555): libfprint-device-DEBUG: 04:23:59.382: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17555): libfprint-device-DEBUG: 04:23:59.383: Updated temperature model after 0.19 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17555): libfprint-virtual_device_connection-DEBUG: 04:23:59.583: Got a new connection!
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.585: Got instructions of length 5
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.585: Received command CONT
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.587: Processing command CONT
(process:17555): libfprint-device-DEBUG: 04:23:59.587: Device reported deletion completion
(process:17555): libfprint-device-DEBUG: 04:23:59.588: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17555): libfprint-device-DEBUG: 04:23:59.589: Updated temperature model after 0.21 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17555): libfprint-virtual_device_connection-DEBUG: 04:23:59.590: Got a new connection!
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.592: Got instructions of length 16
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.592: Received command SET_KEEP_ALIVE 0
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.593: Keep alive toggled: 0
(process:17555): libfprint-virtual_device_connection-DEBUG: 04:23:59.595: Got a new connection!
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.597: Got instructions of length 19
(process:17555): libfprint-virtual_device-DEBUG: 04:23:59.597: Received command SET_ENROLL_STAGES 5
(process:17555): libfprint-device-DEBUG: 04:23:59.599: Device reported close completion
(process:17555): libfprint-device-DEBUG: 04:23:59.600: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17555): libfprint-device-DEBUG: 04:23:59.600: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
----------------------------------------------------------------------
Ran 1 test in 0.667s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:827: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 62/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_duplicate_enroll
start time: 04:23:59
duration: 0.87s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 MALLOC_PERTURB_=153 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_duplicate_enroll
----------------------------------- stdout -----------------------------------
(process:17576): libfprint-context-DEBUG: 04:23:59.865: Initializing FpContext (libfprint version 1.94.6)
(process:17576): libfprint-context-DEBUG: 04:23:59.897: No driver found for USB device 1D6B:0003
(process:17576): libfprint-context-DEBUG: 04:23:59.897: No driver found for USB device 0BDA:5401
(process:17576): libfprint-context-DEBUG: 04:23:59.898: No driver found for USB device 1D6B:0002
(process:17576): libfprint-context-DEBUG: 04:23:59.898: No driver found for USB device 1D6B:0003
(process:17576): libfprint-context-DEBUG: 04:23:59.899: No driver found for USB device 0624:0249
(process:17576): libfprint-context-DEBUG: 04:23:59.899: No driver found for USB device 0624:0248
(process:17576): libfprint-context-DEBUG: 04:23:59.900: No driver found for USB device 1D6B:0002
(process:17576): libfprint-context-DEBUG: 04:23:59.900: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-n_knxzzr/virtual-device-storage.socket
(process:17576): libfprint-context-DEBUG: 04:23:59.902: created
(process:17576): libfprint-device-DEBUG: 04:23:59.915: Device reported probe completion
(process:17576): libfprint-device-DEBUG: 04:23:59.916: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17576): libfprint-device-DEBUG: 04:23:59.916: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:17576): libfprint-virtual_device-DEBUG: 04:23:59.920: 38977939518139: ../libfprint/drivers/virtual-device.c:387
(process:17576): libfprint-virtual_device_connection-DEBUG: 04:23:59.922: 38977939519855: ../libfprint/drivers/virtual-device-listener.c:153
(process:17576): libfprint-device-DEBUG: 04:23:59.925: Device reported open completion
(process:17576): libfprint-device-DEBUG: 04:23:59.926: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17576): libfprint-device-DEBUG: 04:23:59.927: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17576): libfprint-virtual_device_connection-DEBUG: 04:23:59.931: Got a new connection!
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.934: Got instructions of length 14
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.934: Received command SCAN testprint
(process:17576): libfprint-device-DEBUG: 04:23:59.941: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.942: Processing command SCAN testprint
(process:17576): libfprint-device-DEBUG: 04:23:59.942: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17576): libfprint-device-DEBUG: 04:23:59.943: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17576): libfprint-device-DEBUG: 04:23:59.943: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17576): libfprint-device-DEBUG: 04:23:59.944: Device reported enroll progress, reported 1 of 5 have been completed
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.945: Sleeping completed
(process:17576): libfprint-virtual_device_connection-DEBUG: 04:23:59.947: Got a new connection!
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.948: Got instructions of length 14
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.949: Received command SCAN testprint
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.949: Processing command SCAN testprint
(process:17576): libfprint-device-DEBUG: 04:23:59.949: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17576): libfprint-device-DEBUG: 04:23:59.950: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17576): libfprint-device-DEBUG: 04:23:59.951: Device reported enroll progress, reported 2 of 5 have been completed
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.952: Sleeping completed
(process:17576): libfprint-virtual_device_connection-DEBUG: 04:23:59.954: Got a new connection!
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.956: Got instructions of length 14
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.956: Received command SCAN testprint
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.957: Processing command SCAN testprint
(process:17576): libfprint-device-DEBUG: 04:23:59.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17576): libfprint-device-DEBUG: 04:23:59.958: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17576): libfprint-device-DEBUG: 04:23:59.958: Device reported enroll progress, reported 3 of 5 have been completed
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.959: Sleeping completed
(process:17576): libfprint-virtual_device_connection-DEBUG: 04:23:59.962: Got a new connection!
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.963: Got instructions of length 14
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.964: Received command SCAN testprint
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.964: Processing command SCAN testprint
(process:17576): libfprint-device-DEBUG: 04:23:59.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17576): libfprint-device-DEBUG: 04:23:59.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17576): libfprint-device-DEBUG: 04:23:59.965: Device reported enroll progress, reported 4 of 5 have been completed
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.967: Sleeping completed
(process:17576): libfprint-virtual_device_connection-DEBUG: 04:23:59.969: Got a new connection!
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.970: Got instructions of length 14
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.971: Received command SCAN testprint
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.971: Processing command SCAN testprint
(process:17576): libfprint-device-DEBUG: 04:23:59.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17576): libfprint-device-DEBUG: 04:23:59.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17576): libfprint-device-DEBUG: 04:23:59.972: Device reported enroll progress, reported 5 of 5 have been completed
(process:17576): libfprint-device-DEBUG: 04:23:59.973: Device reported enroll completion
(process:17576): libfprint-device-DEBUG: 04:23:59.973: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17576): libfprint-device-DEBUG: 04:23:59.974: Print for finger FP_FINGER_LEFT_LITTLE enrolled
(process:17576): libfprint-device-DEBUG: 04:23:59.975: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17576): libfprint-device-DEBUG: 04:23:59.976: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17576): libfprint-virtual_device_connection-DEBUG: 04:23:59.983: Got a new connection!
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.985: Got instructions of length 14
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.985: Received command SCAN testprint
(process:17576): libfprint-device-DEBUG: 04:23:59.987: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.988: Processing command SCAN testprint
(process:17576): libfprint-device-DEBUG: 04:23:59.988: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17576): libfprint-device-DEBUG: 04:23:59.989: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17576): libfprint-device-DEBUG: 04:23:59.989: Device reported enroll completion
(process:17576): libfprint-device-DEBUG: 04:23:59.990: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17576): libfprint-device-DEBUG: 04:23:59.990: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17576): libfprint-device-DEBUG: 04:23:59.991: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17576): libfprint-virtual_device_connection-DEBUG: 04:23:59.993: Got a new connection!
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.995: Got instructions of length 5
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.995: Received command CONT
(process:17576): libfprint-virtual_device-DEBUG: 04:23:59.997: Processing command CONT
(process:17576): libfprint-device-DEBUG: 04:23:59.997: Device reported deletion completion
(process:17576): libfprint-device-DEBUG: 04:23:59.998: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17576): libfprint-device-DEBUG: 04:23:59.999: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17576): libfprint-virtual_device_connection-DEBUG: 04:24:00.000: Got a new connection!
(process:17576): libfprint-virtual_device-DEBUG: 04:24:00.002: Got instructions of length 16
(process:17576): libfprint-virtual_device-DEBUG: 04:24:00.002: Received command SET_KEEP_ALIVE 0
(process:17576): libfprint-virtual_device-DEBUG: 04:24:00.003: Keep alive toggled: 0
(process:17576): libfprint-virtual_device_connection-DEBUG: 04:24:00.005: Got a new connection!
(process:17576): libfprint-virtual_device-DEBUG: 04:24:00.006: Got instructions of length 19
(process:17576): libfprint-virtual_device-DEBUG: 04:24:00.007: Received command SET_ENROLL_STAGES 5
(process:17576): libfprint-device-DEBUG: 04:24:00.009: Device reported close completion
(process:17576): libfprint-device-DEBUG: 04:24:00.010: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17576): libfprint-device-DEBUG: 04:24:00.010: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
Enroll done
ok
(process:17576): libfprint-virtual_device_storage-DEBUG: 04:24:00.013: 38977939611155: ../libfprint/drivers/virtual-device-storage.c:253
(process:17576): libfprint-virtual_device-DEBUG: 04:24:00.013: 38977939611672: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.177s
OK
==============================================================================
=================================== 63/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_device_sleep_before_completing_verify
start time: 04:23:58
duration: 1.57s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=25 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_device_sleep_before_completing_verify
----------------------------------- stdout -----------------------------------
(process:17563): libfprint-context-DEBUG: 04:23:58.977: Initializing FpContext (libfprint version 1.94.6)
(process:17563): libfprint-context-DEBUG: 04:23:59.012: No driver found for USB device 1D6B:0003
(process:17563): libfprint-context-DEBUG: 04:23:59.013: No driver found for USB device 0BDA:5401
(process:17563): libfprint-context-DEBUG: 04:23:59.014: No driver found for USB device 1D6B:0002
(process:17563): libfprint-context-DEBUG: 04:23:59.014: No driver found for USB device 1D6B:0003
(process:17563): libfprint-context-DEBUG: 04:23:59.015: No driver found for USB device 0624:0249
(process:17563): libfprint-context-DEBUG: 04:23:59.015: No driver found for USB device 0624:0248
(process:17563): libfprint-context-DEBUG: 04:23:59.016: No driver found for USB device 1D6B:0002
(process:17563): libfprint-context-DEBUG: 04:23:59.016: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-pusr_qzy/virtual-device-storage.socket
(process:17563): libfprint-context-DEBUG: 04:23:59.018: created
(process:17563): libfprint-device-DEBUG: 04:23:59.029: Device reported probe completion
(process:17563): libfprint-device-DEBUG: 04:23:59.030: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17563): libfprint-device-DEBUG: 04:23:59.031: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:17563): libfprint-virtual_device-DEBUG: 04:23:59.036: 38977938633744: ../libfprint/drivers/virtual-device.c:387
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:23:59.037: 38977938635455: ../libfprint/drivers/virtual-device-listener.c:153
(process:17563): libfprint-device-DEBUG: 04:23:59.041: Device reported open completion
(process:17563): libfprint-device-DEBUG: 04:23:59.042: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17563): libfprint-device-DEBUG: 04:23:59.043: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:23:59.048: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.051: Got instructions of length 14
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.051: Received command SCAN foo-print
(process:17563): libfprint-device-DEBUG: 04:23:59.059: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.059: Processing command SCAN foo-print
(process:17563): libfprint-device-DEBUG: 04:23:59.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17563): libfprint-device-DEBUG: 04:23:59.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17563): libfprint-device-DEBUG: 04:23:59.061: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17563): libfprint-device-DEBUG: 04:23:59.061: Device reported enroll progress, reported 1 of 5 have been completed
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.063: Sleeping completed
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:23:59.065: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.066: Got instructions of length 14
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.067: Received command SCAN foo-print
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.067: Processing command SCAN foo-print
(process:17563): libfprint-device-DEBUG: 04:23:59.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17563): libfprint-device-DEBUG: 04:23:59.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17563): libfprint-device-DEBUG: 04:23:59.069: Device reported enroll progress, reported 2 of 5 have been completed
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.070: Sleeping completed
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:23:59.073: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.074: Got instructions of length 14
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.075: Received command SCAN foo-print
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.075: Processing command SCAN foo-print
(process:17563): libfprint-device-DEBUG: 04:23:59.078: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17563): libfprint-device-DEBUG: 04:23:59.078: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17563): libfprint-device-DEBUG: 04:23:59.079: Device reported enroll progress, reported 3 of 5 have been completed
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.081: Sleeping completed
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:23:59.083: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.085: Got instructions of length 14
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.085: Received command SCAN foo-print
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.086: Processing command SCAN foo-print
(process:17563): libfprint-device-DEBUG: 04:23:59.086: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17563): libfprint-device-DEBUG: 04:23:59.087: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17563): libfprint-device-DEBUG: 04:23:59.087: Device reported enroll progress, reported 4 of 5 have been completed
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.088: Sleeping completed
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:23:59.091: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.092: Got instructions of length 14
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.093: Received command SCAN foo-print
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.093: Processing command SCAN foo-print
(process:17563): libfprint-device-DEBUG: 04:23:59.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17563): libfprint-device-DEBUG: 04:23:59.094: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17563): libfprint-device-DEBUG: 04:23:59.094: Device reported enroll progress, reported 5 of 5 have been completed
(process:17563): libfprint-device-DEBUG: 04:23:59.095: Device reported enroll completion
(process:17563): libfprint-device-DEBUG: 04:23:59.095: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17563): libfprint-device-DEBUG: 04:23:59.096: Print for finger FP_FINGER_LEFT_RING enrolled
(process:17563): libfprint-device-DEBUG: 04:23:59.097: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17563): libfprint-device-DEBUG: 04:23:59.098: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:23:59.105: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.106: Got instructions of length 9
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.107: Received command SLEEP 100
(process:17563): libfprint-device-DEBUG: 04:23:59.112: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.113: Processing command SLEEP 100
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.113: Sleeping 100ms
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:23:59.115: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.116: Got instructions of length 14
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.117: Received command SCAN bar-print
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:23:59.119: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.121: Got instructions of length 9
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.121: Received command SLEEP 800
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.214: Sleeping completed
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.214: Processing command SCAN bar-print
(process:17563): libfprint-device-DEBUG: 04:23:59.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17563): libfprint-device-DEBUG: 04:23:59.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17563): libfprint-virtual_device_storage-DEBUG: 04:23:59.215: Trying to identify print 'bar-print' against a gallery of 1 prints
(process:17563): libfprint-device-DEBUG: 04:23:59.215: Device reported identify result
(process:17563): libfprint-device-DEBUG: 04:23:59.215: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.216: Processing command SLEEP 800
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.217: Sleeping 800ms
(process:17563): libfprint-virtual_device-DEBUG: 04:23:59.217: Sleeping now, command queued for later: SCAN bar-print
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.018: Sleeping completed
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.018: Processing command SCAN bar-print
(process:17563): libfprint-device-DEBUG: 04:24:00.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17563): libfprint-virtual_device_storage-DEBUG: 04:24:00.019: Trying to identify print 'bar-print' against a gallery of 1 prints
(process:17563): libfprint-device-DEBUG: 04:24:00.019: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17563): libfprint-device-DEBUG: 04:24:00.019: Device reported identify completion
(process:17563): libfprint-device-DEBUG: 04:24:00.020: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17563): libfprint-device-DEBUG: 04:24:00.020: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17563): libfprint-device-DEBUG: 04:24:00.020: Updated temperature model after 0.91 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:24:00.023: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.024: Got instructions of length 5
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.025: Received command CONT
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.026: Processing command CONT
(process:17563): libfprint-device-DEBUG: 04:24:00.026: Device reported deletion completion
(process:17563): libfprint-device-DEBUG: 04:24:00.026: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17563): libfprint-device-DEBUG: 04:24:00.027: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:24:00.028: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.029: Got instructions of length 16
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.029: Received command SET_KEEP_ALIVE 0
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.029: Keep alive toggled: 0
(process:17563): libfprint-virtual_device_connection-DEBUG: 04:24:00.032: Got a new connection!
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.035: Got instructions of length 19
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.050: Received command SET_ENROLL_STAGES 5
(process:17563): libfprint-device-DEBUG: 04:24:00.052: Device reported close completion
(process:17563): libfprint-device-DEBUG: 04:24:00.052: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17563): libfprint-device-DEBUG: 04:24:00.052: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17563): libfprint-virtual_device_storage-DEBUG: 04:24:00.055: 38977939652905: ../libfprint/drivers/virtual-device-storage.c:253
(process:17563): libfprint-virtual_device-DEBUG: 04:24:00.055: 38977939653066: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 1.089s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:865: DeprecationWarning: FPrint.Device.supports_identify is deprecated
self.start_verify(enrolled, identify=self.dev.supports_identify())
==============================================================================
=================================== 64/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll
start time: 04:23:59
duration: 0.64s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=173 UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_enroll
----------------------------------- stdout -----------------------------------
(process:17578): libfprint-context-DEBUG: 04:24:00.042: Initializing FpContext (libfprint version 1.94.6)
(process:17578): libfprint-context-DEBUG: 04:24:00.076: No driver found for USB device 1D6B:0003
(process:17578): libfprint-context-DEBUG: 04:24:00.077: No driver found for USB device 0BDA:5401
(process:17578): libfprint-context-DEBUG: 04:24:00.077: No driver found for USB device 1D6B:0002
(process:17578): libfprint-context-DEBUG: 04:24:00.077: No driver found for USB device 1D6B:0003
(process:17578): libfprint-context-DEBUG: 04:24:00.078: No driver found for USB device 0624:0249
(process:17578): libfprint-context-DEBUG: 04:24:00.079: No driver found for USB device 0624:0248
(process:17578): libfprint-context-DEBUG: 04:24:00.079: No driver found for USB device 1D6B:0002
(process:17578): libfprint-context-DEBUG: 04:24:00.079: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-7qdneepv/virtual-device-storage.socket
(process:17578): libfprint-context-DEBUG: 04:24:00.082: created
(process:17578): libfprint-device-DEBUG: 04:24:00.093: Device reported probe completion
(process:17578): libfprint-device-DEBUG: 04:24:00.094: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17578): libfprint-device-DEBUG: 04:24:00.095: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:17578): libfprint-virtual_device-DEBUG: 04:24:00.099: 38977939696846: ../libfprint/drivers/virtual-device.c:387
(process:17578): libfprint-virtual_device_connection-DEBUG: 04:24:00.100: 38977939698545: ../libfprint/drivers/virtual-device-listener.c:153
(process:17578): libfprint-device-DEBUG: 04:24:00.104: Device reported open completion
(process:17578): libfprint-device-DEBUG: 04:24:00.104: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17578): libfprint-device-DEBUG: 04:24:00.105: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17578): libfprint-virtual_device_connection-DEBUG: 04:24:00.110: Got a new connection!
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.112: Got instructions of length 14
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.112: Received command SCAN testprint
(process:17578): libfprint-device-DEBUG: 04:24:00.119: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.120: Processing command SCAN testprint
(process:17578): libfprint-device-DEBUG: 04:24:00.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17578): libfprint-device-DEBUG: 04:24:00.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17578): libfprint-device-DEBUG: 04:24:00.122: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17578): libfprint-device-DEBUG: 04:24:00.122: Device reported enroll progress, reported 1 of 5 have been completed
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.124: Sleeping completed
(process:17578): libfprint-virtual_device_connection-DEBUG: 04:24:00.125: Got a new connection!
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.127: Got instructions of length 14
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.127: Received command SCAN testprint
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.128: Processing command SCAN testprint
(process:17578): libfprint-device-DEBUG: 04:24:00.128: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17578): libfprint-device-DEBUG: 04:24:00.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17578): libfprint-device-DEBUG: 04:24:00.129: Device reported enroll progress, reported 2 of 5 have been completed
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.130: Sleeping completed
(process:17578): libfprint-virtual_device_connection-DEBUG: 04:24:00.133: Got a new connection!
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.134: Got instructions of length 14
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.135: Received command SCAN testprint
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.135: Processing command SCAN testprint
(process:17578): libfprint-device-DEBUG: 04:24:00.135: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17578): libfprint-device-DEBUG: 04:24:00.136: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17578): libfprint-device-DEBUG: 04:24:00.136: Device reported enroll progress, reported 3 of 5 have been completed
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.138: Sleeping completed
(process:17578): libfprint-virtual_device_connection-DEBUG: 04:24:00.140: Got a new connection!
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.141: Got instructions of length 14
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.142: Received command SCAN testprint
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.143: Processing command SCAN testprint
(process:17578): libfprint-device-DEBUG: 04:24:00.143: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17578): libfprint-device-DEBUG: 04:24:00.143: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17578): libfprint-device-DEBUG: 04:24:00.144: Device reported enroll progress, reported 4 of 5 have been completed
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.145: Sleeping completed
(process:17578): libfprint-virtual_device_connection-DEBUG: 04:24:00.147: Got a new connection!
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.149: Got instructions of length 14
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.149: Received command SCAN testprint
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.150: Processing command SCAN testprint
(process:17578): libfprint-device-DEBUG: 04:24:00.150: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17578): libfprint-device-DEBUG: 04:24:00.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17578): libfprint-device-DEBUG: 04:24:00.151: Device reported enroll progress, reported 5 of 5 have been completed
(process:17578): libfprint-device-DEBUG: 04:24:00.152: Device reported enroll completion
(process:17578): libfprint-device-DEBUG: 04:24:00.152: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17578): libfprint-device-DEBUG: 04:24:00.153: Print for finger FP_FINGER_LEFT_LITTLE enrolled
(process:17578): libfprint-device-DEBUG: 04:24:00.154: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17578): libfprint-device-DEBUG: 04:24:00.155: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17578): libfprint-virtual_device_connection-DEBUG: 04:24:00.163: Got a new connection!
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.164: Got instructions of length 5
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.165: Received command CONT
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.174: Processing command CONT
(process:17578): libfprint-device-DEBUG: 04:24:00.174: Device reported deletion completion
(process:17578): libfprint-device-DEBUG: 04:24:00.174: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17578): libfprint-device-DEBUG: 04:24:00.174: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17578): libfprint-virtual_device_connection-DEBUG: 04:24:00.176: Got a new connection!
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.177: Got instructions of length 16
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.177: Received command SET_KEEP_ALIVE 0
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.177: Keep alive toggled: 0
(process:17578): libfprint-virtual_device_connection-DEBUG: 04:24:00.180: Got a new connection!
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.181: Got instructions of length 19
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.181: Received command SET_ENROLL_STAGES 5
(process:17578): libfprint-device-DEBUG: 04:24:00.192: Device reported close completion
(process:17578): libfprint-device-DEBUG: 04:24:00.192: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17578): libfprint-device-DEBUG: 04:24:00.193: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17578): libfprint-virtual_device_storage-DEBUG: 04:24:00.195: 38977939792976: ../libfprint/drivers/virtual-device-storage.c:253
(process:17578): libfprint-virtual_device-DEBUG: 04:24:00.195: 38977939793126: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.174s
OK
==============================================================================
=================================== 65/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_device_sleep_on_cancellation
start time: 04:23:58
duration: 2.20s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=173 UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_device_sleep_on_cancellation
----------------------------------- stdout -----------------------------------
(process:17565): libfprint-context-DEBUG: 04:23:59.150: Initializing FpContext (libfprint version 1.94.6)
(process:17565): libfprint-context-DEBUG: 04:23:59.182: No driver found for USB device 1D6B:0003
(process:17565): libfprint-context-DEBUG: 04:23:59.182: No driver found for USB device 0BDA:5401
(process:17565): libfprint-context-DEBUG: 04:23:59.182: No driver found for USB device 1D6B:0002
(process:17565): libfprint-context-DEBUG: 04:23:59.183: No driver found for USB device 1D6B:0003
(process:17565): libfprint-context-DEBUG: 04:23:59.183: No driver found for USB device 0624:0249
(process:17565): libfprint-context-DEBUG: 04:23:59.183: No driver found for USB device 0624:0248
(process:17565): libfprint-context-DEBUG: 04:23:59.183: No driver found for USB device 1D6B:0002
(process:17565): libfprint-context-DEBUG: 04:23:59.183: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-92geofq7/virtual-device-storage.socket
(process:17565): libfprint-context-DEBUG: 04:23:59.185: created
(process:17565): libfprint-device-DEBUG: 04:23:59.196: Device reported probe completion
(process:17565): libfprint-device-DEBUG: 04:23:59.197: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17565): libfprint-device-DEBUG: 04:23:59.197: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:17565): libfprint-virtual_device-DEBUG: 04:23:59.201: 38977938799171: ../libfprint/drivers/virtual-device.c:387
(process:17565): libfprint-virtual_device_connection-DEBUG: 04:23:59.203: 38977938801008: ../libfprint/drivers/virtual-device-listener.c:153
(process:17565): libfprint-device-DEBUG: 04:23:59.207: Device reported open completion
(process:17565): libfprint-device-DEBUG: 04:23:59.207: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17565): libfprint-device-DEBUG: 04:23:59.208: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17565): libfprint-virtual_device_connection-DEBUG: 04:23:59.211: Got a new connection!
(process:17565): libfprint-virtual_device-DEBUG: 04:23:59.213: Got instructions of length 26
(process:17565): libfprint-virtual_device-DEBUG: 04:23:59.215: Received command SET_CANCELLATION_ENABLED 0
(process:17565): libfprint-virtual_device-DEBUG: 04:23:59.216: Cancellation support toggled: 0
(process:17565): libfprint-virtual_device_connection-DEBUG: 04:23:59.218: Got a new connection!
(process:17565): libfprint-virtual_device-DEBUG: 04:23:59.219: Got instructions of length 10
(process:17565): libfprint-virtual_device-DEBUG: 04:23:59.219: Received command SLEEP 1500
(process:17565): libfprint-virtual_device_connection-DEBUG: 04:23:59.221: Got a new connection!
(process:17565): libfprint-virtual_device-DEBUG: 04:23:59.223: Got instructions of length 14
(process:17565): libfprint-virtual_device-DEBUG: 04:23:59.223: Received command SCAN foo-print
(process:17565): libfprint-device-DEBUG: 04:23:59.231: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17565): libfprint-virtual_device-DEBUG: 04:23:59.232: Processing command SLEEP 1500
(process:17565): libfprint-virtual_device-DEBUG: 04:23:59.232: Sleeping 1500ms
(process:17565): libfprint-device-DEBUG: 04:23:59.337: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17565): libfprint-device-DEBUG: 04:23:59.534: Idle cancelling on ongoing operation!
(process:17565): libfprint-virtual_device-DEBUG: 04:24:00.738: Sleeping completed
(process:17565): libfprint-device-DEBUG: 04:24:00.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17565): libfprint-device-DEBUG: 04:24:00.738: Device reported identify completion
(process:17565): libfprint-device-DEBUG: 04:24:00.738: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17565): libfprint-device-DEBUG: 04:24:00.739: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17565): libfprint-device-DEBUG: 04:24:00.739: Updated temperature model after 1.40 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17565): libfprint-virtual_device-DEBUG: 04:24:00.744: Processing command SCAN foo-print
(process:17565): libfprint-device-DEBUG: 04:24:00.744: Device reported close completion
(process:17565): libfprint-device-DEBUG: 04:24:00.745: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17565): libfprint-device-DEBUG: 04:24:00.745: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
----------------------------------------------------------------------
Ran 1 test in 1.637s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:844: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 66/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_script_interactive
start time: 04:24:00
duration: 0.80s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=150 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_enroll_script_interactive
----------------------------------- stdout -----------------------------------
(process:17589): libfprint-context-DEBUG: 04:24:00.579: Initializing FpContext (libfprint version 1.94.6)
(process:17589): libfprint-context-DEBUG: 04:24:00.612: No driver found for USB device 1D6B:0003
(process:17589): libfprint-context-DEBUG: 04:24:00.613: No driver found for USB device 0BDA:5401
(process:17589): libfprint-context-DEBUG: 04:24:00.613: No driver found for USB device 1D6B:0002
(process:17589): libfprint-context-DEBUG: 04:24:00.614: No driver found for USB device 1D6B:0003
(process:17589): libfprint-context-DEBUG: 04:24:00.614: No driver found for USB device 0624:0249
(process:17589): libfprint-context-DEBUG: 04:24:00.615: No driver found for USB device 0624:0248
(process:17589): libfprint-context-DEBUG: 04:24:00.615: No driver found for USB device 1D6B:0002
(process:17589): libfprint-context-DEBUG: 04:24:00.616: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-rc_xxwxw/virtual-device-storage.socket
(process:17589): libfprint-context-DEBUG: 04:24:00.617: created
(process:17589): libfprint-device-DEBUG: 04:24:00.629: Device reported probe completion
(process:17589): libfprint-device-DEBUG: 04:24:00.630: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17589): libfprint-device-DEBUG: 04:24:00.631: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:17589): libfprint-virtual_device-DEBUG: 04:24:00.635: 38977940232962: ../libfprint/drivers/virtual-device.c:387
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.636: 38977940234713: ../libfprint/drivers/virtual-device-listener.c:153
(process:17589): libfprint-device-DEBUG: 04:24:00.640: Device reported open completion
(process:17589): libfprint-device-DEBUG: 04:24:00.654: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17589): libfprint-device-DEBUG: 04:24:00.655: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.658: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.660: Got instructions of length 8
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.661: Received command SLEEP 50
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.663: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.664: Got instructions of length 13
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.665: Received command SCAN print-id
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.667: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.669: Got instructions of length 13
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.682: Received command SCAN print-id
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.686: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.687: Got instructions of length 7
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.688: Received command RETRY 1
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.690: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.691: Got instructions of length 13
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.692: Received command SCAN print-id
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.694: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.695: Got instructions of length 8
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.698: Received command SLEEP 50
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.701: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.703: Got instructions of length 13
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.703: Received command SCAN print-id
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.705: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.707: Got instructions of length 7
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.707: Received command RETRY 2
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.710: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.712: Got instructions of length 15
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.712: Received command SCAN another-id
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.714: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.716: Got instructions of length 13
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.716: Received command SCAN print-id
(process:17589): libfprint-device-DEBUG: 04:24:00.723: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.723: Processing command SLEEP 50
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.724: Sleeping 50ms
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.778: Sleeping completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.778: Processing command SCAN print-id
(process:17589): libfprint-device-DEBUG: 04:24:00.778: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17589): libfprint-device-DEBUG: 04:24:00.778: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17589): libfprint-device-DEBUG: 04:24:00.779: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17589): libfprint-device-DEBUG: 04:24:00.779: Device reported enroll progress, reported 1 of 5 have been completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.779: Sleeping completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.779: Processing command SCAN print-id
(process:17589): libfprint-device-DEBUG: 04:24:00.780: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17589): libfprint-device-DEBUG: 04:24:00.780: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17589): libfprint-device-DEBUG: 04:24:00.780: Device reported enroll progress, reported 2 of 5 have been completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.780: Sleeping completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.780: Processing command RETRY 1
(process:17589): libfprint-device-DEBUG: 04:24:00.781: Device reported enroll progress, reported 2 of 5 have been completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.781: Sleeping completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.781: Processing command SCAN print-id
(process:17589): libfprint-device-DEBUG: 04:24:00.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17589): libfprint-device-DEBUG: 04:24:00.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17589): libfprint-device-DEBUG: 04:24:00.782: Device reported enroll progress, reported 3 of 5 have been completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.782: Processing command SLEEP 50
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.782: Sleeping 50ms
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.834: Sleeping completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.834: Processing command SCAN print-id
(process:17589): libfprint-device-DEBUG: 04:24:00.834: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17589): libfprint-device-DEBUG: 04:24:00.834: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17589): libfprint-device-DEBUG: 04:24:00.835: Device reported enroll progress, reported 4 of 5 have been completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.835: Sleeping completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.835: Processing command RETRY 2
(process:17589): libfprint-device-DEBUG: 04:24:00.835: Device reported enroll progress, reported 4 of 5 have been completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.836: Sleeping completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.836: Processing command SCAN another-id
(process:17589): libfprint-device-DEBUG: 04:24:00.836: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17589): libfprint-device-DEBUG: 04:24:00.836: Device reported enroll progress, reported 4 of 5 have been completed
(process:17589): libfprint-device-DEBUG: 04:24:00.837: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.837: Sleeping completed
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.837: Processing command SCAN print-id
(process:17589): libfprint-device-DEBUG: 04:24:00.837: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17589): libfprint-device-DEBUG: 04:24:00.837: Device reported enroll progress, reported 5 of 5 have been completed
(process:17589): libfprint-device-DEBUG: 04:24:00.838: Device reported enroll completion
(process:17589): libfprint-device-DEBUG: 04:24:00.838: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17589): libfprint-device-DEBUG: 04:24:00.838: Print for finger FP_FINGER_UNKNOWN enrolled
(process:17589): libfprint-device-DEBUG: 04:24:00.838: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17589): libfprint-device-DEBUG: 04:24:00.839: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.847: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.848: Got instructions of length 5
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.849: Received command CONT
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.850: Processing command CONT
(process:17589): libfprint-device-DEBUG: 04:24:00.850: Device reported deletion completion
(process:17589): libfprint-device-DEBUG: 04:24:00.850: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17589): libfprint-device-DEBUG: 04:24:00.851: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.852: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.853: Got instructions of length 16
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.853: Received command SET_KEEP_ALIVE 0
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.853: Keep alive toggled: 0
(process:17589): libfprint-virtual_device_connection-DEBUG: 04:24:00.860: Got a new connection!
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.861: Got instructions of length 19
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.861: Received command SET_ENROLL_STAGES 5
(process:17589): libfprint-device-DEBUG: 04:24:00.869: Device reported close completion
(process:17589): libfprint-device-DEBUG: 04:24:00.869: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17589): libfprint-device-DEBUG: 04:24:00.870: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
(process:17589): libfprint-virtual_device_storage-DEBUG: 04:24:00.871: 38977940469688: ../libfprint/drivers/virtual-device-storage.c:253
(process:17589): libfprint-virtual_device-DEBUG: 04:24:00.872: 38977940469828: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.310s
OK
==============================================================================
=================================== 67/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_script
start time: 04:24:00
duration: 0.94s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=193 NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_enroll_script
----------------------------------- stdout -----------------------------------
(process:17587): libfprint-context-DEBUG: 04:24:00.703: Initializing FpContext (libfprint version 1.94.6)
(process:17587): libfprint-context-DEBUG: 04:24:00.737: No driver found for USB device 1D6B:0003
(process:17587): libfprint-context-DEBUG: 04:24:00.737: No driver found for USB device 0BDA:5401
(process:17587): libfprint-context-DEBUG: 04:24:00.737: No driver found for USB device 1D6B:0002
(process:17587): libfprint-context-DEBUG: 04:24:00.737: No driver found for USB device 1D6B:0003
(process:17587): libfprint-context-DEBUG: 04:24:00.737: No driver found for USB device 0624:0249
(process:17587): libfprint-context-DEBUG: 04:24:00.738: No driver found for USB device 0624:0248
(process:17587): libfprint-context-DEBUG: 04:24:00.738: No driver found for USB device 1D6B:0002
(process:17587): libfprint-context-DEBUG: 04:24:00.738: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-i9d3a_63/virtual-device-storage.socket
(process:17587): libfprint-context-DEBUG: 04:24:00.740: created
(process:17587): libfprint-device-DEBUG: 04:24:00.752: Device reported probe completion
(process:17587): libfprint-device-DEBUG: 04:24:00.753: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17587): libfprint-device-DEBUG: 04:24:00.753: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:17587): libfprint-virtual_device-DEBUG: 04:24:00.761: 38977940359506: ../libfprint/drivers/virtual-device.c:387
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.763: 38977940360900: ../libfprint/drivers/virtual-device-listener.c:153
(process:17587): libfprint-device-DEBUG: 04:24:00.766: Device reported open completion
(process:17587): libfprint-device-DEBUG: 04:24:00.767: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17587): libfprint-device-DEBUG: 04:24:00.767: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.770: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.772: Got instructions of length 19
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.772: Received command SET_ENROLL_STAGES 8
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.774: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.775: Got instructions of length 13
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.775: Received command SCAN print-id
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.777: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.783: Got instructions of length 13
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.784: Received command SCAN print-id
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.787: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.789: Got instructions of length 7
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.789: Received command RETRY 1
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.792: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.793: Got instructions of length 13
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.793: Received command SCAN print-id
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.796: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.797: Got instructions of length 7
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.797: Received command RETRY 3
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.800: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.801: Got instructions of length 13
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.801: Received command SCAN print-id
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.804: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.805: Got instructions of length 7
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.806: Received command RETRY 2
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.808: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.809: Got instructions of length 13
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.810: Received command SCAN print-id
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.812: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.813: Got instructions of length 8
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.814: Received command SLEEP 10
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.816: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.817: Got instructions of length 8
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.818: Received command SLEEP 20
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.820: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.821: Got instructions of length 7
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.822: Received command RETRY 0
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.824: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.825: Got instructions of length 7
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.826: Received command RETRY 3
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.828: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.830: Got instructions of length 13
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.831: Received command SCAN print-id
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.833: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.837: Got instructions of length 15
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.838: Received command SCAN another-id
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.841: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.843: Got instructions of length 13
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.843: Received command SCAN print-id
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.845: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.847: Got instructions of length 13
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.847: Received command SCAN print-id
(process:17587): libfprint-device-DEBUG: 04:24:00.854: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.855: Processing command SCAN print-id
(process:17587): libfprint-device-DEBUG: 04:24:00.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17587): libfprint-device-DEBUG: 04:24:00.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17587): libfprint-device-DEBUG: 04:24:00.857: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17587): libfprint-device-DEBUG: 04:24:00.857: Device reported enroll progress, reported 1 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.858: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.858: Processing command SCAN print-id
(process:17587): libfprint-device-DEBUG: 04:24:00.858: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17587): libfprint-device-DEBUG: 04:24:00.859: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17587): libfprint-device-DEBUG: 04:24:00.859: Device reported enroll progress, reported 2 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.860: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.861: Processing command RETRY 1
(process:17587): libfprint-device-DEBUG: 04:24:00.866: Device reported enroll progress, reported 2 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.866: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.867: Processing command SCAN print-id
(process:17587): libfprint-device-DEBUG: 04:24:00.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17587): libfprint-device-DEBUG: 04:24:00.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17587): libfprint-device-DEBUG: 04:24:00.868: Device reported enroll progress, reported 3 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.869: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.869: Processing command RETRY 3
(process:17587): libfprint-device-DEBUG: 04:24:00.870: Device reported enroll progress, reported 3 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.871: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.871: Processing command SCAN print-id
(process:17587): libfprint-device-DEBUG: 04:24:00.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17587): libfprint-device-DEBUG: 04:24:00.873: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17587): libfprint-device-DEBUG: 04:24:00.873: Device reported enroll progress, reported 4 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.874: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.881: Processing command RETRY 2
(process:17587): libfprint-device-DEBUG: 04:24:00.881: Device reported enroll progress, reported 4 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.882: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.882: Processing command SCAN print-id
(process:17587): libfprint-device-DEBUG: 04:24:00.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17587): libfprint-device-DEBUG: 04:24:00.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17587): libfprint-device-DEBUG: 04:24:00.882: Device reported enroll progress, reported 5 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.882: Processing command SLEEP 10
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.882: Sleeping 10ms
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.894: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.894: Processing command SLEEP 20
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.894: Sleeping 20ms
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.918: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.918: Processing command RETRY 0
(process:17587): libfprint-device-DEBUG: 04:24:00.918: Device reported enroll progress, reported 5 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.918: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.919: Processing command RETRY 3
(process:17587): libfprint-device-DEBUG: 04:24:00.919: Device reported enroll progress, reported 5 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.919: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.919: Processing command SCAN print-id
(process:17587): libfprint-device-DEBUG: 04:24:00.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17587): libfprint-device-DEBUG: 04:24:00.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17587): libfprint-device-DEBUG: 04:24:00.920: Device reported enroll progress, reported 6 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.920: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.920: Processing command SCAN another-id
(process:17587): libfprint-device-DEBUG: 04:24:00.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17587): libfprint-device-DEBUG: 04:24:00.920: Device reported enroll progress, reported 6 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.920: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.921: Processing command SCAN print-id
(process:17587): libfprint-device-DEBUG: 04:24:00.921: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17587): libfprint-device-DEBUG: 04:24:00.921: Device reported enroll progress, reported 7 of 8 have been completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.921: Sleeping completed
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.921: Processing command SCAN print-id
(process:17587): libfprint-device-DEBUG: 04:24:00.921: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17587): libfprint-device-DEBUG: 04:24:00.922: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17587): libfprint-device-DEBUG: 04:24:00.922: Device reported enroll progress, reported 8 of 8 have been completed
(process:17587): libfprint-device-DEBUG: 04:24:00.922: Device reported enroll completion
(process:17587): libfprint-device-DEBUG: 04:24:00.922: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17587): libfprint-device-DEBUG: 04:24:00.922: Print for finger FP_FINGER_UNKNOWN enrolled
(process:17587): libfprint-device-DEBUG: 04:24:00.923: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17587): libfprint-device-DEBUG: 04:24:00.923: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.926: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.927: Got instructions of length 5
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.927: Received command CONT
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.929: Processing command CONT
(process:17587): libfprint-device-DEBUG: 04:24:00.929: Device reported deletion completion
(process:17587): libfprint-device-DEBUG: 04:24:00.929: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17587): libfprint-device-DEBUG: 04:24:00.929: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.939: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.941: Got instructions of length 16
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.941: Received command SET_KEEP_ALIVE 0
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.941: Keep alive toggled: 0
(process:17587): libfprint-virtual_device_connection-DEBUG: 04:24:00.947: Got a new connection!
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.949: Got instructions of length 19
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.949: Received command SET_ENROLL_STAGES 5
(process:17587): libfprint-device-DEBUG: 04:24:00.959: Device reported close completion
(process:17587): libfprint-device-DEBUG: 04:24:00.960: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17587): libfprint-device-DEBUG: 04:24:00.961: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
(process:17587): libfprint-virtual_device_storage-DEBUG: 04:24:00.963: 38977940561436: ../libfprint/drivers/virtual-device-storage.c:253
(process:17587): libfprint-virtual_device-DEBUG: 04:24:00.964: 38977940561912: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.286s
OK
==============================================================================
=================================== 68/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_verify_error
start time: 04:24:00
duration: 1.08s
result: exit status 0
command: MALLOC_PERTURB_=70 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_enroll_verify_error
----------------------------------- stdout -----------------------------------
(process:17591): libfprint-context-DEBUG: 04:24:00.885: Initializing FpContext (libfprint version 1.94.6)
(process:17591): libfprint-context-DEBUG: 04:24:00.941: No driver found for USB device 1D6B:0003
(process:17591): libfprint-context-DEBUG: 04:24:00.942: No driver found for USB device 0BDA:5401
(process:17591): libfprint-context-DEBUG: 04:24:00.942: No driver found for USB device 1D6B:0002
(process:17591): libfprint-context-DEBUG: 04:24:00.942: No driver found for USB device 1D6B:0003
(process:17591): libfprint-context-DEBUG: 04:24:00.942: No driver found for USB device 0624:0249
(process:17591): libfprint-context-DEBUG: 04:24:00.942: No driver found for USB device 0624:0248
(process:17591): libfprint-context-DEBUG: 04:24:00.942: No driver found for USB device 1D6B:0002
(process:17591): libfprint-context-DEBUG: 04:24:00.943: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-ky5746k8/virtual-device-storage.socket
(process:17591): libfprint-context-DEBUG: 04:24:00.944: created
(process:17591): libfprint-device-DEBUG: 04:24:00.966: Device reported probe completion
(process:17591): libfprint-device-DEBUG: 04:24:00.978: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17591): libfprint-device-DEBUG: 04:24:00.978: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:17591): libfprint-virtual_device-DEBUG: 04:24:00.982: 38977940579773: ../libfprint/drivers/virtual-device.c:387
(process:17591): libfprint-virtual_device_connection-DEBUG: 04:24:00.987: 38977940585218: ../libfprint/drivers/virtual-device-listener.c:153
(process:17591): libfprint-device-DEBUG: 04:24:00.990: Device reported open completion
(process:17591): libfprint-device-DEBUG: 04:24:00.990: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17591): libfprint-device-DEBUG: 04:24:00.991: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17591): libfprint-virtual_device_connection-DEBUG: 04:24:01.003: Got a new connection!
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.005: Got instructions of length 14
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.005: Received command SCAN testprint
(process:17591): libfprint-device-DEBUG: 04:24:01.211: Updated temperature model after 0.22 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.211: Processing command SCAN testprint
(process:17591): libfprint-device-DEBUG: 04:24:01.211: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17591): libfprint-device-DEBUG: 04:24:01.211: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17591): libfprint-device-DEBUG: 04:24:01.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17591): libfprint-device-DEBUG: 04:24:01.212: Device reported enroll progress, reported 1 of 5 have been completed
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.213: Sleeping completed
(process:17591): libfprint-virtual_device_connection-DEBUG: 04:24:01.214: Got a new connection!
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.215: Got instructions of length 14
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.215: Received command SCAN testprint
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.215: Processing command SCAN testprint
(process:17591): libfprint-device-DEBUG: 04:24:01.216: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17591): libfprint-device-DEBUG: 04:24:01.216: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17591): libfprint-device-DEBUG: 04:24:01.216: Device reported enroll progress, reported 2 of 5 have been completed
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.217: Sleeping completed
(process:17591): libfprint-virtual_device_connection-DEBUG: 04:24:01.219: Got a new connection!
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.220: Got instructions of length 14
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.220: Received command SCAN testprint
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.220: Processing command SCAN testprint
(process:17591): libfprint-device-DEBUG: 04:24:01.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17591): libfprint-device-DEBUG: 04:24:01.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17591): libfprint-device-DEBUG: 04:24:01.221: Device reported enroll progress, reported 3 of 5 have been completed
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.222: Sleeping completed
(process:17591): libfprint-virtual_device_connection-DEBUG: 04:24:01.232: Got a new connection!
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.233: Got instructions of length 14
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.233: Received command SCAN testprint
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.233: Processing command SCAN testprint
(process:17591): libfprint-device-DEBUG: 04:24:01.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17591): libfprint-device-DEBUG: 04:24:01.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17591): libfprint-device-DEBUG: 04:24:01.234: Device reported enroll progress, reported 4 of 5 have been completed
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.235: Sleeping completed
(process:17591): libfprint-virtual_device_connection-DEBUG: 04:24:01.236: Got a new connection!
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.238: Got instructions of length 14
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.238: Received command SCAN testprint
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.238: Processing command SCAN testprint
(process:17591): libfprint-device-DEBUG: 04:24:01.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17591): libfprint-device-DEBUG: 04:24:01.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17591): libfprint-device-DEBUG: 04:24:01.238: Device reported enroll progress, reported 5 of 5 have been completed
(process:17591): libfprint-device-DEBUG: 04:24:01.238: Device reported enroll completion
(process:17591): libfprint-device-DEBUG: 04:24:01.239: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17591): libfprint-device-DEBUG: 04:24:01.239: Print for finger FP_FINGER_LEFT_RING enrolled
(process:17591): libfprint-device-DEBUG: 04:24:01.240: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17591): libfprint-device-DEBUG: 04:24:01.240: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17591): libfprint-virtual_device_connection-DEBUG: 04:24:01.253: Got a new connection!
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.262: Got instructions of length 7
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.262: Received command ERROR 0
(process:17591): libfprint-device-DEBUG: 04:24:01.265: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.265: Processing command ERROR 0
(process:17591): libfprint-device-DEBUG: 04:24:01.266: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17591): libfprint-device-DEBUG: 04:24:01.266: Device reported identify completion
(process:17591): libfprint-device-DEBUG: 04:24:01.266: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17591): libfprint-device-DEBUG: 04:24:01.266: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17591): libfprint-device-DEBUG: 04:24:01.266: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17591): libfprint-virtual_device_connection-DEBUG: 04:24:01.269: Got a new connection!
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.270: Got instructions of length 5
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.270: Received command CONT
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.271: Processing command CONT
(process:17591): libfprint-device-DEBUG: 04:24:01.272: Device reported deletion completion
(process:17591): libfprint-device-DEBUG: 04:24:01.272: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17591): libfprint-device-DEBUG: 04:24:01.272: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17591): libfprint-virtual_device_connection-DEBUG: 04:24:01.273: Got a new connection!
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.283: Got instructions of length 16
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.283: Received command SET_KEEP_ALIVE 0
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.283: Keep alive toggled: 0
(process:17591): libfprint-virtual_device_connection-DEBUG: 04:24:01.285: Got a new connection!
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.286: Got instructions of length 19
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.286: Received command SET_ENROLL_STAGES 5
(process:17591): libfprint-device-DEBUG: 04:24:01.288: Device reported close completion
(process:17591): libfprint-device-DEBUG: 04:24:01.288: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17591): libfprint-device-DEBUG: 04:24:01.288: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
Enroll done
ok
(process:17591): libfprint-virtual_device_storage-DEBUG: 04:24:01.290: 38977940888652: ../libfprint/drivers/virtual-device-storage.c:253
(process:17591): libfprint-virtual_device-DEBUG: 04:24:01.291: 38977940888799: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.430s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:606: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 69/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_verify_retry
start time: 04:24:01
duration: 0.65s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=75 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_enroll_verify_retry
----------------------------------- stdout -----------------------------------
(process:17606): libfprint-context-DEBUG: 04:24:01.517: Initializing FpContext (libfprint version 1.94.6)
(process:17606): libfprint-context-DEBUG: 04:24:01.552: No driver found for USB device 1D6B:0003
(process:17606): libfprint-context-DEBUG: 04:24:01.552: No driver found for USB device 0BDA:5401
(process:17606): libfprint-context-DEBUG: 04:24:01.553: No driver found for USB device 1D6B:0002
(process:17606): libfprint-context-DEBUG: 04:24:01.553: No driver found for USB device 1D6B:0003
(process:17606): libfprint-context-DEBUG: 04:24:01.553: No driver found for USB device 0624:0249
(process:17606): libfprint-context-DEBUG: 04:24:01.553: No driver found for USB device 0624:0248
(process:17606): libfprint-context-DEBUG: 04:24:01.553: No driver found for USB device 1D6B:0002
(process:17606): libfprint-context-DEBUG: 04:24:01.553: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-22ktfsvy/virtual-device-storage.socket
(process:17606): libfprint-context-DEBUG: 04:24:01.560: created
(process:17606): libfprint-device-DEBUG: 04:24:01.576: Device reported probe completion
(process:17606): libfprint-device-DEBUG: 04:24:01.577: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17606): libfprint-device-DEBUG: 04:24:01.577: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:17606): libfprint-virtual_device-DEBUG: 04:24:01.589: 38977941186801: ../libfprint/drivers/virtual-device.c:387
(process:17606): libfprint-virtual_device_connection-DEBUG: 04:24:01.594: 38977941192333: ../libfprint/drivers/virtual-device-listener.c:153
(process:17606): libfprint-device-DEBUG: 04:24:01.597: Device reported open completion
(process:17606): libfprint-device-DEBUG: 04:24:01.598: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17606): libfprint-device-DEBUG: 04:24:01.602: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17606): libfprint-virtual_device_connection-DEBUG: 04:24:01.617: Got a new connection!
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.619: Got instructions of length 7
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.619: Received command RETRY 1
(process:17606): libfprint-device-DEBUG: 04:24:01.627: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.627: Processing command RETRY 1
(process:17606): libfprint-device-DEBUG: 04:24:01.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.628: Virtual device scan failed with error: The swipe was too short, please try again.
(process:17606): libfprint-device-DEBUG: 04:24:01.628: Device reported verify result
(process:17606): libfprint-device-DEBUG: 04:24:01.628: Device reported verify completion
(process:17606): libfprint-device-DEBUG: 04:24:01.628: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17606): libfprint-device-DEBUG: 04:24:01.629: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17606): libfprint-device-DEBUG: 04:24:01.629: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17606): libfprint-virtual_device_connection-DEBUG: 04:24:01.633: Got a new connection!
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.640: Got instructions of length 5
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.640: Received command CONT
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.642: Processing command CONT
(process:17606): libfprint-device-DEBUG: 04:24:01.642: Device reported deletion completion
(process:17606): libfprint-device-DEBUG: 04:24:01.642: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17606): libfprint-device-DEBUG: 04:24:01.642: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17606): libfprint-virtual_device_connection-DEBUG: 04:24:01.644: Got a new connection!
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.645: Got instructions of length 16
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.645: Received command SET_KEEP_ALIVE 0
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.645: Keep alive toggled: 0
(process:17606): libfprint-virtual_device_connection-DEBUG: 04:24:01.651: Got a new connection!
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.652: Got instructions of length 19
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.653: Received command SET_ENROLL_STAGES 5
(process:17606): libfprint-device-DEBUG: 04:24:01.654: Device reported close completion
(process:17606): libfprint-device-DEBUG: 04:24:01.655: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17606): libfprint-device-DEBUG: 04:24:01.655: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17606): libfprint-virtual_device_storage-DEBUG: 04:24:01.657: 38977941255118: ../libfprint/drivers/virtual-device-storage.c:253
(process:17606): libfprint-virtual_device-DEBUG: 04:24:01.657: 38977941255282: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.166s
OK
==============================================================================
=================================== 70/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_verify_no_match
start time: 04:24:00
duration: 0.87s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=238 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_enroll_verify_no_match
----------------------------------- stdout -----------------------------------
(process:17604): libfprint-context-DEBUG: 04:24:01.576: Initializing FpContext (libfprint version 1.94.6)
(process:17604): libfprint-context-DEBUG: 04:24:01.613: No driver found for USB device 1D6B:0003
(process:17604): libfprint-context-DEBUG: 04:24:01.613: No driver found for USB device 0BDA:5401
(process:17604): libfprint-context-DEBUG: 04:24:01.614: No driver found for USB device 1D6B:0002
(process:17604): libfprint-context-DEBUG: 04:24:01.614: No driver found for USB device 1D6B:0003
(process:17604): libfprint-context-DEBUG: 04:24:01.615: No driver found for USB device 0624:0249
(process:17604): libfprint-context-DEBUG: 04:24:01.615: No driver found for USB device 0624:0248
(process:17604): libfprint-context-DEBUG: 04:24:01.616: No driver found for USB device 1D6B:0002
(process:17604): libfprint-context-DEBUG: 04:24:01.616: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-k3sbg8pf/virtual-device-storage.socket
(process:17604): libfprint-context-DEBUG: 04:24:01.618: created
(process:17604): libfprint-device-DEBUG: 04:24:01.636: Device reported probe completion
(process:17604): libfprint-device-DEBUG: 04:24:01.637: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17604): libfprint-device-DEBUG: 04:24:01.637: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:17604): libfprint-virtual_device-DEBUG: 04:24:01.643: 38977941241295: ../libfprint/drivers/virtual-device.c:387
(process:17604): libfprint-virtual_device_connection-DEBUG: 04:24:01.646: 38977941243789: ../libfprint/drivers/virtual-device-listener.c:153
(process:17604): libfprint-device-DEBUG: 04:24:01.649: Device reported open completion
(process:17604): libfprint-device-DEBUG: 04:24:01.650: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17604): libfprint-device-DEBUG: 04:24:01.650: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17604): libfprint-virtual_device_connection-DEBUG: 04:24:01.658: Got a new connection!
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.660: Got instructions of length 14
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.660: Received command SCAN testprint
(process:17604): libfprint-device-DEBUG: 04:24:01.667: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.669: Processing command SCAN testprint
(process:17604): libfprint-device-DEBUG: 04:24:01.669: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17604): libfprint-device-DEBUG: 04:24:01.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17604): libfprint-device-DEBUG: 04:24:01.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17604): libfprint-device-DEBUG: 04:24:01.671: Device reported enroll progress, reported 1 of 5 have been completed
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.673: Sleeping completed
(process:17604): libfprint-virtual_device_connection-DEBUG: 04:24:01.675: Got a new connection!
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.677: Got instructions of length 14
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.677: Received command SCAN testprint
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.678: Processing command SCAN testprint
(process:17604): libfprint-device-DEBUG: 04:24:01.678: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17604): libfprint-device-DEBUG: 04:24:01.679: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17604): libfprint-device-DEBUG: 04:24:01.680: Device reported enroll progress, reported 2 of 5 have been completed
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.681: Sleeping completed
(process:17604): libfprint-virtual_device_connection-DEBUG: 04:24:01.683: Got a new connection!
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.686: Got instructions of length 14
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.686: Received command SCAN testprint
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.687: Processing command SCAN testprint
(process:17604): libfprint-device-DEBUG: 04:24:01.687: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17604): libfprint-device-DEBUG: 04:24:01.688: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17604): libfprint-device-DEBUG: 04:24:01.688: Device reported enroll progress, reported 3 of 5 have been completed
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.690: Sleeping completed
(process:17604): libfprint-virtual_device_connection-DEBUG: 04:24:01.692: Got a new connection!
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.693: Got instructions of length 14
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.694: Received command SCAN testprint
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.694: Processing command SCAN testprint
(process:17604): libfprint-device-DEBUG: 04:24:01.695: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17604): libfprint-device-DEBUG: 04:24:01.695: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17604): libfprint-device-DEBUG: 04:24:01.696: Device reported enroll progress, reported 4 of 5 have been completed
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.697: Sleeping completed
(process:17604): libfprint-virtual_device_connection-DEBUG: 04:24:01.700: Got a new connection!
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.701: Got instructions of length 14
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.702: Received command SCAN testprint
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.702: Processing command SCAN testprint
(process:17604): libfprint-device-DEBUG: 04:24:01.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17604): libfprint-device-DEBUG: 04:24:01.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17604): libfprint-device-DEBUG: 04:24:01.704: Device reported enroll progress, reported 5 of 5 have been completed
(process:17604): libfprint-device-DEBUG: 04:24:01.704: Device reported enroll completion
(process:17604): libfprint-device-DEBUG: 04:24:01.705: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17604): libfprint-device-DEBUG: 04:24:01.705: Print for finger FP_FINGER_LEFT_RING enrolled
(process:17604): libfprint-device-DEBUG: 04:24:01.707: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17604): libfprint-device-DEBUG: 04:24:01.707: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17604): libfprint-virtual_device_connection-DEBUG: 04:24:01.719: Got a new connection!
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.721: Got instructions of length 18
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.722: Received command SCAN not-testprint
(process:17604): libfprint-device-DEBUG: 04:24:01.726: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.727: Processing command SCAN not-testprint
(process:17604): libfprint-device-DEBUG: 04:24:01.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17604): libfprint-device-DEBUG: 04:24:01.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17604): libfprint-virtual_device_storage-DEBUG: 04:24:01.729: Trying to identify print 'not-testprint' against a gallery of 1 prints
(process:17604): libfprint-device-DEBUG: 04:24:01.729: Device reported identify result
(process:17604): libfprint-device-DEBUG: 04:24:01.730: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17604): libfprint-device-DEBUG: 04:24:01.731: Device reported identify completion
(process:17604): libfprint-device-DEBUG: 04:24:01.731: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17604): libfprint-device-DEBUG: 04:24:01.732: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17604): libfprint-device-DEBUG: 04:24:01.732: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17604): libfprint-virtual_device_connection-DEBUG: 04:24:01.735: Got a new connection!
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.738: Got instructions of length 5
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.738: Received command CONT
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.740: Processing command CONT
(process:17604): libfprint-device-DEBUG: 04:24:01.741: Device reported deletion completion
(process:17604): libfprint-device-DEBUG: 04:24:01.742: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17604): libfprint-device-DEBUG: 04:24:01.742: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17604): libfprint-virtual_device_connection-DEBUG: 04:24:01.744: Got a new connection!
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.745: Got instructions of length 16
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.746: Received command SET_KEEP_ALIVE 0
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.748: Keep alive toggled: 0
(process:17604): libfprint-virtual_device_connection-DEBUG: 04:24:01.751: Got a new connection!
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.752: Got instructions of length 19
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.753: Received command SET_ENROLL_STAGES 5
(process:17604): libfprint-device-DEBUG: 04:24:01.755: Device reported close completion
(process:17604): libfprint-device-DEBUG: 04:24:01.756: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17604): libfprint-device-DEBUG: 04:24:01.756: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17604): libfprint-virtual_device_storage-DEBUG: 04:24:01.759: 38977941357513: ../libfprint/drivers/virtual-device-storage.c:253
(process:17604): libfprint-virtual_device-DEBUG: 04:24:01.760: 38977941358070: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.202s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:599: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 71/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_verify_match
start time: 04:24:00
duration: 1.07s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=203 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_enroll_verify_match
----------------------------------- stdout -----------------------------------
(process:17599): libfprint-context-DEBUG: 04:24:01.555: Initializing FpContext (libfprint version 1.94.6)
(process:17599): libfprint-context-DEBUG: 04:24:01.624: No driver found for USB device 1D6B:0003
(process:17599): libfprint-context-DEBUG: 04:24:01.624: No driver found for USB device 0BDA:5401
(process:17599): libfprint-context-DEBUG: 04:24:01.625: No driver found for USB device 1D6B:0002
(process:17599): libfprint-context-DEBUG: 04:24:01.625: No driver found for USB device 1D6B:0003
(process:17599): libfprint-context-DEBUG: 04:24:01.625: No driver found for USB device 0624:0249
(process:17599): libfprint-context-DEBUG: 04:24:01.625: No driver found for USB device 0624:0248
(process:17599): libfprint-context-DEBUG: 04:24:01.625: No driver found for USB device 1D6B:0002
(process:17599): libfprint-context-DEBUG: 04:24:01.625: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-c9fzbzk0/virtual-device-storage.socket
(process:17599): libfprint-context-DEBUG: 04:24:01.635: created
(process:17599): libfprint-device-DEBUG: 04:24:01.668: Device reported probe completion
(process:17599): libfprint-device-DEBUG: 04:24:01.668: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17599): libfprint-device-DEBUG: 04:24:01.668: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:17599): libfprint-virtual_device-DEBUG: 04:24:01.672: 38977941269766: ../libfprint/drivers/virtual-device.c:387
(process:17599): libfprint-virtual_device_connection-DEBUG: 04:24:01.673: 38977941271128: ../libfprint/drivers/virtual-device-listener.c:153
(process:17599): libfprint-device-DEBUG: 04:24:01.684: Device reported open completion
(process:17599): libfprint-device-DEBUG: 04:24:01.684: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17599): libfprint-device-DEBUG: 04:24:01.685: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17599): libfprint-virtual_device_connection-DEBUG: 04:24:01.689: Got a new connection!
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.699: Got instructions of length 14
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.699: Received command SCAN testprint
(process:17599): libfprint-device-DEBUG: 04:24:01.710: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.710: Processing command SCAN testprint
(process:17599): libfprint-device-DEBUG: 04:24:01.710: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17599): libfprint-device-DEBUG: 04:24:01.711: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17599): libfprint-device-DEBUG: 04:24:01.711: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17599): libfprint-device-DEBUG: 04:24:01.711: Device reported enroll progress, reported 1 of 5 have been completed
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.712: Sleeping completed
(process:17599): libfprint-virtual_device_connection-DEBUG: 04:24:01.714: Got a new connection!
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.719: Got instructions of length 14
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.719: Received command SCAN testprint
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.719: Processing command SCAN testprint
(process:17599): libfprint-device-DEBUG: 04:24:01.719: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17599): libfprint-device-DEBUG: 04:24:01.719: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17599): libfprint-device-DEBUG: 04:24:01.720: Device reported enroll progress, reported 2 of 5 have been completed
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.721: Sleeping completed
(process:17599): libfprint-virtual_device_connection-DEBUG: 04:24:01.723: Got a new connection!
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.724: Got instructions of length 14
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.724: Received command SCAN testprint
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.724: Processing command SCAN testprint
(process:17599): libfprint-device-DEBUG: 04:24:01.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17599): libfprint-device-DEBUG: 04:24:01.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17599): libfprint-device-DEBUG: 04:24:01.724: Device reported enroll progress, reported 3 of 5 have been completed
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.725: Sleeping completed
(process:17599): libfprint-virtual_device_connection-DEBUG: 04:24:01.735: Got a new connection!
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.737: Got instructions of length 14
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.737: Received command SCAN testprint
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.737: Processing command SCAN testprint
(process:17599): libfprint-device-DEBUG: 04:24:01.737: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17599): libfprint-device-DEBUG: 04:24:01.737: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17599): libfprint-device-DEBUG: 04:24:01.737: Device reported enroll progress, reported 4 of 5 have been completed
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.738: Sleeping completed
(process:17599): libfprint-virtual_device_connection-DEBUG: 04:24:01.740: Got a new connection!
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.746: Got instructions of length 14
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.746: Received command SCAN testprint
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.746: Processing command SCAN testprint
(process:17599): libfprint-device-DEBUG: 04:24:01.746: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17599): libfprint-device-DEBUG: 04:24:01.746: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17599): libfprint-device-DEBUG: 04:24:01.747: Device reported enroll progress, reported 5 of 5 have been completed
(process:17599): libfprint-device-DEBUG: 04:24:01.747: Device reported enroll completion
(process:17599): libfprint-device-DEBUG: 04:24:01.747: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17599): libfprint-device-DEBUG: 04:24:01.747: Print for finger FP_FINGER_LEFT_THUMB enrolled
(process:17599): libfprint-device-DEBUG: 04:24:01.748: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17599): libfprint-device-DEBUG: 04:24:01.748: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17599): libfprint-virtual_device_connection-DEBUG: 04:24:01.765: Got a new connection!
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.766: Got instructions of length 14
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.766: Received command SCAN testprint
(process:17599): libfprint-device-DEBUG: 04:24:01.776: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.776: Processing command SCAN testprint
(process:17599): libfprint-device-DEBUG: 04:24:01.776: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17599): libfprint-device-DEBUG: 04:24:01.776: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17599): libfprint-virtual_device_storage-DEBUG: 04:24:01.777: Trying to identify print 'testprint' against a gallery of 1 prints
(process:17599): libfprint-device-DEBUG: 04:24:01.777: Device reported identify result
(process:17599): libfprint-device-DEBUG: 04:24:01.777: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17599): libfprint-device-DEBUG: 04:24:01.778: Device reported identify completion
(process:17599): libfprint-device-DEBUG: 04:24:01.778: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17599): libfprint-device-DEBUG: 04:24:01.778: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17599): libfprint-device-DEBUG: 04:24:01.778: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17599): libfprint-virtual_device_connection-DEBUG: 04:24:01.781: Got a new connection!
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.790: Got instructions of length 5
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.790: Received command CONT
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.792: Processing command CONT
(process:17599): libfprint-device-DEBUG: 04:24:01.792: Device reported deletion completion
(process:17599): libfprint-device-DEBUG: 04:24:01.792: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17599): libfprint-device-DEBUG: 04:24:01.793: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17599): libfprint-virtual_device_connection-DEBUG: 04:24:01.794: Got a new connection!
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.795: Got instructions of length 16
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.795: Received command SET_KEEP_ALIVE 0
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.796: Keep alive toggled: 0
(process:17599): libfprint-virtual_device_connection-DEBUG: 04:24:01.797: Got a new connection!
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.802: Got instructions of length 19
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.803: Received command SET_ENROLL_STAGES 5
(process:17599): libfprint-device-DEBUG: 04:24:01.804: Device reported close completion
(process:17599): libfprint-device-DEBUG: 04:24:01.805: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17599): libfprint-device-DEBUG: 04:24:01.805: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17599): libfprint-virtual_device_storage-DEBUG: 04:24:01.808: 38977941405757: ../libfprint/drivers/virtual-device-storage.c:253
(process:17599): libfprint-virtual_device-DEBUG: 04:24:01.808: 38977941405936: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.286s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:593: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 72/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_finger_status
start time: 04:24:01
duration: 0.59s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=147 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_finger_status
----------------------------------- stdout -----------------------------------
(process:17621): libfprint-context-DEBUG: 04:24:02.252: Initializing FpContext (libfprint version 1.94.6)
(process:17621): libfprint-context-DEBUG: 04:24:02.286: No driver found for USB device 1D6B:0003
(process:17621): libfprint-context-DEBUG: 04:24:02.286: No driver found for USB device 0BDA:5401
(process:17621): libfprint-context-DEBUG: 04:24:02.286: No driver found for USB device 1D6B:0002
(process:17621): libfprint-context-DEBUG: 04:24:02.286: No driver found for USB device 1D6B:0003
(process:17621): libfprint-context-DEBUG: 04:24:02.286: No driver found for USB device 0624:0249
(process:17621): libfprint-context-DEBUG: 04:24:02.287: No driver found for USB device 0624:0248
(process:17621): libfprint-context-DEBUG: 04:24:02.287: No driver found for USB device 1D6B:0002
(process:17621): libfprint-context-DEBUG: 04:24:02.287: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-7v50azfb/virtual-device-storage.socket
(process:17621): libfprint-context-DEBUG: 04:24:02.289: created
(process:17621): libfprint-device-DEBUG: 04:24:02.300: Device reported probe completion
(process:17621): libfprint-device-DEBUG: 04:24:02.301: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17621): libfprint-device-DEBUG: 04:24:02.301: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:17621): libfprint-virtual_device-DEBUG: 04:24:02.304: 38977941902579: ../libfprint/drivers/virtual-device.c:387
(process:17621): libfprint-virtual_device_connection-DEBUG: 04:24:02.306: 38977941903897: ../libfprint/drivers/virtual-device-listener.c:153
(process:17621): libfprint-device-DEBUG: 04:24:02.309: Device reported open completion
(process:17621): libfprint-device-DEBUG: 04:24:02.309: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17621): libfprint-device-DEBUG: 04:24:02.309: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17621): libfprint-device-DEBUG: 04:24:02.317: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17621): libfprint-device-DEBUG: 04:24:02.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17621): libfprint-virtual_device_connection-DEBUG: 04:24:02.321: Got a new connection!
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.323: Got instructions of length 8
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.323: Received command FINGER 1
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.323: Processing command FINGER 1
(process:17621): libfprint-device-DEBUG: 04:24:02.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17621): libfprint-virtual_device_connection-DEBUG: 04:24:02.325: Got a new connection!
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.327: Got instructions of length 8
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.327: Received command FINGER 0
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.327: Processing command FINGER 0
(process:17621): libfprint-device-DEBUG: 04:24:02.327: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17621): libfprint-device-DEBUG: 04:24:02.328: Idle cancelling on ongoing operation!
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.329: Got cancellation!
(process:17621): libfprint-device-DEBUG: 04:24:02.329: Device reported identify completion
(process:17621): libfprint-device-DEBUG: 04:24:02.329: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17621): libfprint-device-DEBUG: 04:24:02.329: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17621): libfprint-device-DEBUG: 04:24:02.329: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17621): libfprint-virtual_device_connection-DEBUG: 04:24:02.333: Got a new connection!
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.334: Got instructions of length 5
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.335: Received command CONT
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.336: Processing command CONT
(process:17621): libfprint-device-DEBUG: 04:24:02.336: Device reported deletion completion
(process:17621): libfprint-device-DEBUG: 04:24:02.336: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17621): libfprint-device-DEBUG: 04:24:02.337: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17621): libfprint-virtual_device_connection-DEBUG: 04:24:02.338: Got a new connection!
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.339: Got instructions of length 16
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.339: Received command SET_KEEP_ALIVE 0
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.339: Keep alive toggled: 0
(process:17621): libfprint-virtual_device_connection-DEBUG: 04:24:02.341: Got a new connection!
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.343: Got instructions of length 19
(process:17621): libfprint-virtual_device-DEBUG: 04:24:02.343: Received command SET_ENROLL_STAGES 5
(process:17621): libfprint-device-DEBUG: 04:24:02.344: Device reported close completion
(process:17621): libfprint-device-DEBUG: 04:24:02.345: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17621): libfprint-device-DEBUG: 04:24:02.345: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
----------------------------------------------------------------------
Ran 1 test in 0.112s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:732: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 73/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_verify_script
start time: 04:24:01
duration: 1.24s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=193 NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_enroll_verify_script
----------------------------------- stdout -----------------------------------
(process:17608): libfprint-context-DEBUG: 04:24:02.053: Initializing FpContext (libfprint version 1.94.6)
(process:17608): libfprint-context-DEBUG: 04:24:02.109: No driver found for USB device 1D6B:0003
(process:17608): libfprint-context-DEBUG: 04:24:02.110: No driver found for USB device 0BDA:5401
(process:17608): libfprint-context-DEBUG: 04:24:02.110: No driver found for USB device 1D6B:0002
(process:17608): libfprint-context-DEBUG: 04:24:02.114: No driver found for USB device 1D6B:0003
(process:17608): libfprint-context-DEBUG: 04:24:02.114: No driver found for USB device 0624:0249
(process:17608): libfprint-context-DEBUG: 04:24:02.115: No driver found for USB device 0624:0248
(process:17608): libfprint-context-DEBUG: 04:24:02.115: No driver found for USB device 1D6B:0002
(process:17608): libfprint-context-DEBUG: 04:24:02.115: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-jlk5r6k6/virtual-device-storage.socket
(process:17608): libfprint-context-DEBUG: 04:24:02.117: created
(process:17608): libfprint-device-DEBUG: 04:24:02.137: Device reported probe completion
(process:17608): libfprint-device-DEBUG: 04:24:02.138: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17608): libfprint-device-DEBUG: 04:24:02.139: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:17608): libfprint-virtual_device-DEBUG: 04:24:02.152: 38977941749874: ../libfprint/drivers/virtual-device.c:387
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.153: 38977941751634: ../libfprint/drivers/virtual-device-listener.c:153
(process:17608): libfprint-device-DEBUG: 04:24:02.157: Device reported open completion
(process:17608): libfprint-device-DEBUG: 04:24:02.157: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17608): libfprint-device-DEBUG: 04:24:02.162: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.165: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.168: Got instructions of length 19
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.168: Received command SET_ENROLL_STAGES 8
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.175: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.176: Got instructions of length 13
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.177: Received command SCAN print-id
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.179: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.180: Got instructions of length 13
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.181: Received command SCAN print-id
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.193: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.194: Got instructions of length 7
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.195: Received command RETRY 1
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.197: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.198: Got instructions of length 13
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.199: Received command SCAN print-id
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.201: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.202: Got instructions of length 7
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.203: Received command RETRY 3
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.205: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.215: Got instructions of length 13
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.215: Received command SCAN print-id
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.217: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.219: Got instructions of length 7
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.219: Received command RETRY 2
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.221: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.223: Got instructions of length 13
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.223: Received command SCAN print-id
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.226: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.231: Got instructions of length 8
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.232: Received command SLEEP 10
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.234: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.235: Got instructions of length 8
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.236: Received command SLEEP 20
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.238: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.240: Got instructions of length 7
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.240: Received command RETRY 0
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.250: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.252: Got instructions of length 7
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.253: Received command RETRY 3
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.255: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.256: Got instructions of length 13
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.257: Received command SCAN print-id
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.259: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.260: Got instructions of length 15
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.261: Received command SCAN another-id
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.263: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.265: Got instructions of length 13
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.265: Received command SCAN print-id
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.275: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.277: Got instructions of length 13
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.277: Received command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.282: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.283: Processing command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17608): libfprint-device-DEBUG: 04:24:02.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.285: Device reported enroll progress, reported 1 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.285: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.286: Processing command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.287: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17608): libfprint-device-DEBUG: 04:24:02.288: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.288: Device reported enroll progress, reported 2 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.289: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.290: Processing command RETRY 1
(process:17608): libfprint-device-DEBUG: 04:24:02.298: Device reported enroll progress, reported 2 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.299: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.299: Processing command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17608): libfprint-device-DEBUG: 04:24:02.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.301: Device reported enroll progress, reported 3 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.302: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.302: Processing command RETRY 3
(process:17608): libfprint-device-DEBUG: 04:24:02.303: Device reported enroll progress, reported 3 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.303: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.304: Processing command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17608): libfprint-device-DEBUG: 04:24:02.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.305: Device reported enroll progress, reported 4 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.306: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.307: Processing command RETRY 2
(process:17608): libfprint-device-DEBUG: 04:24:02.307: Device reported enroll progress, reported 4 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.308: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.308: Processing command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.309: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17608): libfprint-device-DEBUG: 04:24:02.315: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.315: Device reported enroll progress, reported 5 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.315: Processing command SLEEP 10
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.316: Sleeping 10ms
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.330: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.331: Processing command SLEEP 20
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.331: Sleeping 20ms
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.354: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.354: Processing command RETRY 0
(process:17608): libfprint-device-DEBUG: 04:24:02.354: Device reported enroll progress, reported 5 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.355: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.355: Processing command RETRY 3
(process:17608): libfprint-device-DEBUG: 04:24:02.355: Device reported enroll progress, reported 5 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.355: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.355: Processing command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17608): libfprint-device-DEBUG: 04:24:02.356: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.356: Device reported enroll progress, reported 6 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.356: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.356: Processing command SCAN another-id
(process:17608): libfprint-device-DEBUG: 04:24:02.356: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17608): libfprint-device-DEBUG: 04:24:02.356: Device reported enroll progress, reported 6 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.357: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.357: Processing command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.357: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.357: Device reported enroll progress, reported 7 of 8 have been completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.357: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.358: Processing command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.358: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17608): libfprint-device-DEBUG: 04:24:02.358: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.358: Device reported enroll progress, reported 8 of 8 have been completed
(process:17608): libfprint-device-DEBUG: 04:24:02.358: Device reported enroll completion
(process:17608): libfprint-device-DEBUG: 04:24:02.358: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17608): libfprint-device-DEBUG: 04:24:02.358: Print for finger FP_FINGER_UNKNOWN enrolled
(process:17608): libfprint-device-DEBUG: 04:24:02.359: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17608): libfprint-device-DEBUG: 04:24:02.359: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.363: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.365: Got instructions of length 7
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.365: Received command RETRY 2
(process:17608): libfprint-device-DEBUG: 04:24:02.368: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.368: Processing command RETRY 2
(process:17608): libfprint-device-DEBUG: 04:24:02.369: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.369: Virtual device scan failed with error: The finger was not centered properly, please try again.
(process:17608): libfprint-device-DEBUG: 04:24:02.374: Device reported verify result
(process:17608): libfprint-device-DEBUG: 04:24:02.374: Device reported verify completion
(process:17608): libfprint-device-DEBUG: 04:24:02.375: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17608): libfprint-device-DEBUG: 04:24:02.375: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17608): libfprint-device-DEBUG: 04:24:02.376: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.378: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.380: Got instructions of length 8
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.380: Received command SLEEP 50
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.382: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.384: Got instructions of length 7
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.384: Received command RETRY 1
(process:17608): libfprint-device-DEBUG: 04:24:02.394: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.395: Processing command SLEEP 50
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.395: Sleeping 50ms
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.446: Sleeping completed
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.447: Processing command RETRY 1
(process:17608): libfprint-device-DEBUG: 04:24:02.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.448: Virtual device scan failed with error: The swipe was too short, please try again.
(process:17608): libfprint-device-DEBUG: 04:24:02.448: Device reported verify result
(process:17608): libfprint-device-DEBUG: 04:24:02.449: Device reported verify completion
(process:17608): libfprint-device-DEBUG: 04:24:02.449: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17608): libfprint-device-DEBUG: 04:24:02.451: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17608): libfprint-device-DEBUG: 04:24:02.451: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.462: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.463: Got instructions of length 15
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.463: Received command SCAN another-id
(process:17608): libfprint-device-DEBUG: 04:24:02.464: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.465: Processing command SCAN another-id
(process:17608): libfprint-device-DEBUG: 04:24:02.465: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.465: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.465: Virtual device scanned print another-id
(process:17608): libfprint-device-DEBUG: 04:24:02.466: Device reported verify result
(process:17608): libfprint-device-DEBUG: 04:24:02.466: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.474: Device reported verify completion
(process:17608): libfprint-device-DEBUG: 04:24:02.474: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17608): libfprint-device-DEBUG: 04:24:02.474: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17608): libfprint-device-DEBUG: 04:24:02.475: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.479: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.480: Got instructions of length 13
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.480: Received command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.481: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.482: Processing command SCAN print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.482: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.482: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.482: Virtual device scanned print print-id
(process:17608): libfprint-device-DEBUG: 04:24:02.482: Device reported verify result
(process:17608): libfprint-device-DEBUG: 04:24:02.483: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17608): libfprint-device-DEBUG: 04:24:02.483: Device reported verify completion
(process:17608): libfprint-device-DEBUG: 04:24:02.483: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17608): libfprint-device-DEBUG: 04:24:02.483: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17608): libfprint-device-DEBUG: 04:24:02.483: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.492: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.493: Got instructions of length 5
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.493: Received command CONT
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.495: Processing command CONT
(process:17608): libfprint-device-DEBUG: 04:24:02.495: Device reported deletion completion
(process:17608): libfprint-device-DEBUG: 04:24:02.495: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17608): libfprint-device-DEBUG: 04:24:02.495: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.497: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.506: Got instructions of length 16
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.506: Received command SET_KEEP_ALIVE 0
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.506: Keep alive toggled: 0
(process:17608): libfprint-virtual_device_connection-DEBUG: 04:24:02.508: Got a new connection!
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.510: Got instructions of length 19
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.510: Received command SET_ENROLL_STAGES 5
(process:17608): libfprint-device-DEBUG: 04:24:02.511: Device reported close completion
(process:17608): libfprint-device-DEBUG: 04:24:02.512: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17608): libfprint-device-DEBUG: 04:24:02.512: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
(process:17608): libfprint-virtual_device_storage-DEBUG: 04:24:02.518: 38977942116266: ../libfprint/drivers/virtual-device-storage.c:253
(process:17608): libfprint-virtual_device-DEBUG: 04:24:02.518: 38977942116431: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.498s
OK
==============================================================================
=================================== 74/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_enroll_with_retry
start time: 04:24:01
duration: 0.89s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=135 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_enroll_with_retry
----------------------------------- stdout -----------------------------------
(process:17619): libfprint-context-DEBUG: 04:24:02.394: Initializing FpContext (libfprint version 1.94.6)
(process:17619): libfprint-context-DEBUG: 04:24:02.426: No driver found for USB device 1D6B:0003
(process:17619): libfprint-context-DEBUG: 04:24:02.426: No driver found for USB device 0BDA:5401
(process:17619): libfprint-context-DEBUG: 04:24:02.427: No driver found for USB device 1D6B:0002
(process:17619): libfprint-context-DEBUG: 04:24:02.427: No driver found for USB device 1D6B:0003
(process:17619): libfprint-context-DEBUG: 04:24:02.427: No driver found for USB device 0624:0249
(process:17619): libfprint-context-DEBUG: 04:24:02.427: No driver found for USB device 0624:0248
(process:17619): libfprint-context-DEBUG: 04:24:02.427: No driver found for USB device 1D6B:0002
(process:17619): libfprint-context-DEBUG: 04:24:02.428: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-wdxfchi9/virtual-device-storage.socket
(process:17619): libfprint-context-DEBUG: 04:24:02.429: created
(process:17619): libfprint-device-DEBUG: 04:24:02.441: Device reported probe completion
(process:17619): libfprint-device-DEBUG: 04:24:02.442: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17619): libfprint-device-DEBUG: 04:24:02.442: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:17619): libfprint-virtual_device-DEBUG: 04:24:02.448: 38977942046036: ../libfprint/drivers/virtual-device.c:387
(process:17619): libfprint-virtual_device_connection-DEBUG: 04:24:02.449: 38977942047397: ../libfprint/drivers/virtual-device-listener.c:153
(process:17619): libfprint-device-DEBUG: 04:24:02.456: Device reported open completion
(process:17619): libfprint-device-DEBUG: 04:24:02.457: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17619): libfprint-device-DEBUG: 04:24:02.457: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17619): libfprint-virtual_device_connection-DEBUG: 04:24:02.461: Got a new connection!
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.463: Got instructions of length 14
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.463: Received command SCAN testprint
(process:17619): libfprint-device-DEBUG: 04:24:02.470: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.470: Processing command SCAN testprint
(process:17619): libfprint-device-DEBUG: 04:24:02.470: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17619): libfprint-device-DEBUG: 04:24:02.470: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17619): libfprint-device-DEBUG: 04:24:02.471: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17619): libfprint-device-DEBUG: 04:24:02.471: Device reported enroll progress, reported 1 of 5 have been completed
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.472: Sleeping completed
(process:17619): libfprint-virtual_device_connection-DEBUG: 04:24:02.473: Got a new connection!
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.474: Got instructions of length 14
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.474: Received command SCAN testprint
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.474: Processing command SCAN testprint
(process:17619): libfprint-device-DEBUG: 04:24:02.475: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17619): libfprint-device-DEBUG: 04:24:02.475: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17619): libfprint-device-DEBUG: 04:24:02.475: Device reported enroll progress, reported 2 of 5 have been completed
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.476: Sleeping completed
(process:17619): libfprint-virtual_device_connection-DEBUG: 04:24:02.479: Got a new connection!
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.480: Got instructions of length 7
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.481: Received command RETRY 1
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.481: Processing command RETRY 1
(process:17619): libfprint-device-DEBUG: 04:24:02.481: Device reported enroll progress, reported 2 of 5 have been completed
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.482: Sleeping completed
(process:17619): libfprint-virtual_device_connection-DEBUG: 04:24:02.484: Got a new connection!
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.485: Got instructions of length 14
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.485: Received command SCAN testprint
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.485: Processing command SCAN testprint
(process:17619): libfprint-device-DEBUG: 04:24:02.485: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17619): libfprint-device-DEBUG: 04:24:02.486: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17619): libfprint-device-DEBUG: 04:24:02.486: Device reported enroll progress, reported 3 of 5 have been completed
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.487: Sleeping completed
(process:17619): libfprint-virtual_device_connection-DEBUG: 04:24:02.489: Got a new connection!
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.490: Got instructions of length 14
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.490: Received command SCAN testprint
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.490: Processing command SCAN testprint
(process:17619): libfprint-device-DEBUG: 04:24:02.490: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17619): libfprint-device-DEBUG: 04:24:02.490: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17619): libfprint-device-DEBUG: 04:24:02.491: Device reported enroll progress, reported 4 of 5 have been completed
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.492: Sleeping completed
(process:17619): libfprint-virtual_device_connection-DEBUG: 04:24:02.493: Got a new connection!
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.495: Got instructions of length 14
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.496: Received command SCAN testprint
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.496: Processing command SCAN testprint
(process:17619): libfprint-device-DEBUG: 04:24:02.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17619): libfprint-device-DEBUG: 04:24:02.498: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17619): libfprint-device-DEBUG: 04:24:02.498: Device reported enroll progress, reported 5 of 5 have been completed
(process:17619): libfprint-device-DEBUG: 04:24:02.499: Device reported enroll completion
(process:17619): libfprint-device-DEBUG: 04:24:02.499: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17619): libfprint-device-DEBUG: 04:24:02.499: Print for finger FP_FINGER_LEFT_LITTLE enrolled
(process:17619): libfprint-device-DEBUG: 04:24:02.501: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17619): libfprint-device-DEBUG: 04:24:02.501: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17619): libfprint-virtual_device_connection-DEBUG: 04:24:02.509: Got a new connection!
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.511: Got instructions of length 5
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.512: Received command CONT
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.514: Processing command CONT
(process:17619): libfprint-device-DEBUG: 04:24:02.514: Device reported deletion completion
(process:17619): libfprint-device-DEBUG: 04:24:02.515: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17619): libfprint-device-DEBUG: 04:24:02.516: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17619): libfprint-virtual_device_connection-DEBUG: 04:24:02.517: Got a new connection!
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.519: Got instructions of length 16
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.520: Received command SET_KEEP_ALIVE 0
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.520: Keep alive toggled: 0
(process:17619): libfprint-virtual_device_connection-DEBUG: 04:24:02.522: Got a new connection!
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.524: Got instructions of length 19
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.524: Received command SET_ENROLL_STAGES 5
(process:17619): libfprint-device-DEBUG: 04:24:02.526: Device reported close completion
(process:17619): libfprint-device-DEBUG: 04:24:02.527: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17619): libfprint-device-DEBUG: 04:24:02.527: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
ok
(process:17619): libfprint-virtual_device_storage-DEBUG: 04:24:02.530: 38977942128378: ../libfprint/drivers/virtual-device-storage.c:253
(process:17619): libfprint-virtual_device-DEBUG: 04:24:02.531: 38977942128889: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.162s
OK
==============================================================================
=================================== 75/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_finger_status_after_sleep
start time: 04:24:01
duration: 0.96s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=233 NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_finger_status_after_sleep
----------------------------------- stdout -----------------------------------
(process:17623): libfprint-context-DEBUG: 04:24:02.595: Initializing FpContext (libfprint version 1.94.6)
(process:17623): libfprint-context-DEBUG: 04:24:02.646: No driver found for USB device 1D6B:0003
(process:17623): libfprint-context-DEBUG: 04:24:02.646: No driver found for USB device 0BDA:5401
(process:17623): libfprint-context-DEBUG: 04:24:02.646: No driver found for USB device 1D6B:0002
(process:17623): libfprint-context-DEBUG: 04:24:02.646: No driver found for USB device 1D6B:0003
(process:17623): libfprint-context-DEBUG: 04:24:02.647: No driver found for USB device 0624:0249
(process:17623): libfprint-context-DEBUG: 04:24:02.647: No driver found for USB device 0624:0248
(process:17623): libfprint-context-DEBUG: 04:24:02.647: No driver found for USB device 1D6B:0002
(process:17623): libfprint-context-DEBUG: 04:24:02.647: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-t_vr0db4/virtual-device-storage.socket
(process:17623): libfprint-context-DEBUG: 04:24:02.649: created
(process:17623): libfprint-device-DEBUG: 04:24:02.669: Device reported probe completion
(process:17623): libfprint-device-DEBUG: 04:24:02.678: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17623): libfprint-device-DEBUG: 04:24:02.678: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:17623): libfprint-virtual_device-DEBUG: 04:24:02.682: 38977942279768: ../libfprint/drivers/virtual-device.c:387
(process:17623): libfprint-virtual_device_connection-DEBUG: 04:24:02.683: 38977942281132: ../libfprint/drivers/virtual-device-listener.c:153
(process:17623): libfprint-device-DEBUG: 04:24:02.694: Device reported open completion
(process:17623): libfprint-device-DEBUG: 04:24:02.694: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17623): libfprint-device-DEBUG: 04:24:02.695: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17623): libfprint-virtual_device_connection-DEBUG: 04:24:02.698: Got a new connection!
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.699: Got instructions of length 8
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.700: Received command SLEEP 10
(process:17623): libfprint-device-DEBUG: 04:24:02.716: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.716: Processing command SLEEP 10
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.716: Sleeping 10ms
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.730: Sleeping completed
(process:17623): libfprint-device-DEBUG: 04:24:02.730: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17623): libfprint-virtual_device_connection-DEBUG: 04:24:02.732: Got a new connection!
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.733: Got instructions of length 8
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.733: Received command FINGER 1
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.733: Processing command FINGER 1
(process:17623): libfprint-device-DEBUG: 04:24:02.733: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17623): libfprint-virtual_device_connection-DEBUG: 04:24:02.736: Got a new connection!
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.737: Got instructions of length 8
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.737: Received command FINGER 0
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.737: Processing command FINGER 0
(process:17623): libfprint-device-DEBUG: 04:24:02.737: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17623): libfprint-device-DEBUG: 04:24:02.742: Idle cancelling on ongoing operation!
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.742: Got cancellation!
(process:17623): libfprint-device-DEBUG: 04:24:02.743: Device reported identify completion
(process:17623): libfprint-device-DEBUG: 04:24:02.743: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17623): libfprint-device-DEBUG: 04:24:02.743: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17623): libfprint-device-DEBUG: 04:24:02.743: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17623): libfprint-virtual_device_connection-DEBUG: 04:24:02.755: Got a new connection!
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.756: Got instructions of length 5
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.757: Received command CONT
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.758: Processing command CONT
(process:17623): libfprint-device-DEBUG: 04:24:02.758: Device reported deletion completion
(process:17623): libfprint-device-DEBUG: 04:24:02.758: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17623): libfprint-device-DEBUG: 04:24:02.759: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17623): libfprint-virtual_device_connection-DEBUG: 04:24:02.760: Got a new connection!
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.761: Got instructions of length 16
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.761: Received command SET_KEEP_ALIVE 0
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.761: Keep alive toggled: 0
(process:17623): libfprint-virtual_device_connection-DEBUG: 04:24:02.767: Got a new connection!
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.769: Got instructions of length 19
(process:17623): libfprint-virtual_device-DEBUG: 04:24:02.769: Received command SET_ENROLL_STAGES 5
(process:17623): libfprint-device-DEBUG: 04:24:02.775: Device reported close completion
(process:17623): libfprint-device-DEBUG: 04:24:02.775: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17623): libfprint-device-DEBUG: 04:24:02.775: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok
----------------------------------------------------------------------
Ran 1 test in 0.209s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:749: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 76/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_identify_no_match
start time: 04:24:02
duration: 0.84s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests MALLOC_PERTURB_=194 FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_identify_no_match
----------------------------------- stdout -----------------------------------
(process:17641): libfprint-context-DEBUG: 04:24:03.126: Initializing FpContext (libfprint version 1.94.6)
(process:17641): libfprint-context-DEBUG: 04:24:03.158: No driver found for USB device 1D6B:0003
(process:17641): libfprint-context-DEBUG: 04:24:03.159: No driver found for USB device 0BDA:5401
(process:17641): libfprint-context-DEBUG: 04:24:03.159: No driver found for USB device 1D6B:0002
(process:17641): libfprint-context-DEBUG: 04:24:03.160: No driver found for USB device 1D6B:0003
(process:17641): libfprint-context-DEBUG: 04:24:03.160: No driver found for USB device 0624:0249
(process:17641): libfprint-context-DEBUG: 04:24:03.161: No driver found for USB device 0624:0248
(process:17641): libfprint-context-DEBUG: 04:24:03.161: No driver found for USB device 1D6B:0002
(process:17641): libfprint-context-DEBUG: 04:24:03.162: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-xsg5bb3l/virtual-device-storage.socket
(process:17641): libfprint-context-DEBUG: 04:24:03.163: created
(process:17641): libfprint-device-DEBUG: 04:24:03.179: Device reported probe completion
(process:17641): libfprint-device-DEBUG: 04:24:03.180: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17641): libfprint-device-DEBUG: 04:24:03.180: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:17641): libfprint-virtual_device-DEBUG: 04:24:03.184: 38977942782567: ../libfprint/drivers/virtual-device.c:387
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.188: 38977942786026: ../libfprint/drivers/virtual-device-listener.c:153
(process:17641): libfprint-device-DEBUG: 04:24:03.191: Device reported open completion
(process:17641): libfprint-device-DEBUG: 04:24:03.192: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17641): libfprint-device-DEBUG: 04:24:03.192: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.197: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.199: Got instructions of length 16
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.200: Received command SCAN right-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.208: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.209: Processing command SCAN right-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.209: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-device-DEBUG: 04:24:03.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.211: Device reported enroll progress, reported 1 of 5 have been completed
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.212: Sleeping completed
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.214: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.215: Got instructions of length 16
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.216: Received command SCAN right-thumb
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.216: Processing command SCAN right-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.217: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-device-DEBUG: 04:24:03.217: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.218: Device reported enroll progress, reported 2 of 5 have been completed
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.219: Sleeping completed
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.222: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.224: Got instructions of length 16
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.224: Received command SCAN right-thumb
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.225: Processing command SCAN right-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.225: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-device-DEBUG: 04:24:03.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.226: Device reported enroll progress, reported 3 of 5 have been completed
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.228: Sleeping completed
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.230: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.231: Got instructions of length 16
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.232: Received command SCAN right-thumb
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.232: Processing command SCAN right-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-device-DEBUG: 04:24:03.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.234: Device reported enroll progress, reported 4 of 5 have been completed
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.235: Sleeping completed
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.238: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.239: Got instructions of length 16
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.240: Received command SCAN right-thumb
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.240: Processing command SCAN right-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-device-DEBUG: 04:24:03.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.242: Device reported enroll progress, reported 5 of 5 have been completed
(process:17641): libfprint-device-DEBUG: 04:24:03.242: Device reported enroll completion
(process:17641): libfprint-device-DEBUG: 04:24:03.243: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17641): libfprint-device-DEBUG: 04:24:03.243: Print for finger FP_FINGER_RIGHT_THUMB enrolled
(process:17641): libfprint-device-DEBUG: 04:24:03.244: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17641): libfprint-device-DEBUG: 04:24:03.245: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.255: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.257: Got instructions of length 15
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.257: Received command SCAN left-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.259: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.260: Processing command SCAN left-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.260: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-device-DEBUG: 04:24:03.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.262: Device reported enroll progress, reported 1 of 5 have been completed
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.263: Sleeping completed
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.266: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.268: Got instructions of length 15
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.268: Received command SCAN left-thumb
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.270: Processing command SCAN left-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-device-DEBUG: 04:24:03.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.271: Device reported enroll progress, reported 2 of 5 have been completed
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.272: Sleeping completed
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.275: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.276: Got instructions of length 15
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.277: Received command SCAN left-thumb
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.278: Processing command SCAN left-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.279: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-device-DEBUG: 04:24:03.281: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.281: Device reported enroll progress, reported 3 of 5 have been completed
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.282: Sleeping completed
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.285: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.286: Got instructions of length 15
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.287: Received command SCAN left-thumb
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.287: Processing command SCAN left-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.287: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-device-DEBUG: 04:24:03.288: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.288: Device reported enroll progress, reported 4 of 5 have been completed
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.290: Sleeping completed
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.292: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.293: Got instructions of length 15
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.294: Received command SCAN left-thumb
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.294: Processing command SCAN left-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.295: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-device-DEBUG: 04:24:03.295: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.296: Device reported enroll progress, reported 5 of 5 have been completed
(process:17641): libfprint-device-DEBUG: 04:24:03.297: Device reported enroll completion
(process:17641): libfprint-device-DEBUG: 04:24:03.297: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17641): libfprint-device-DEBUG: 04:24:03.298: Print for finger FP_FINGER_LEFT_THUMB enrolled
(process:17641): libfprint-device-DEBUG: 04:24:03.301: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17641): libfprint-device-DEBUG: 04:24:03.301: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.305: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.307: Got instructions of length 16
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.307: Received command SCAN right-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.313: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.314: Processing command SCAN right-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.314: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.316: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-virtual_device_storage-DEBUG: 04:24:03.317: Trying to identify print 'right-thumb' against a gallery of 1 prints
(process:17641): libfprint-device-DEBUG: 04:24:03.318: Device reported identify result
(process:17641): libfprint-device-DEBUG: 04:24:03.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.320: Device reported identify completion
(process:17641): libfprint-device-DEBUG: 04:24:03.320: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17641): libfprint-device-DEBUG: 04:24:03.321: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17641): libfprint-device-DEBUG: 04:24:03.322: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.325: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.326: Got instructions of length 15
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.327: Received command SCAN left-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.329: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.329: Processing command SCAN left-thumb
(process:17641): libfprint-device-DEBUG: 04:24:03.330: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.331: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17641): libfprint-virtual_device_storage-DEBUG: 04:24:03.333: Trying to identify print 'left-thumb' against a gallery of 1 prints
(process:17641): libfprint-device-DEBUG: 04:24:03.334: Device reported identify result
(process:17641): libfprint-device-DEBUG: 04:24:03.335: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17641): libfprint-device-DEBUG: 04:24:03.336: Device reported identify completion
(process:17641): libfprint-device-DEBUG: 04:24:03.336: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17641): libfprint-device-DEBUG: 04:24:03.337: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17641): libfprint-device-DEBUG: 04:24:03.337: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.340: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.342: Got instructions of length 5
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.343: Received command CONT
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.345: Processing command CONT
(process:17641): libfprint-device-DEBUG: 04:24:03.345: Device reported deletion completion
(process:17641): libfprint-device-DEBUG: 04:24:03.346: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17641): libfprint-device-DEBUG: 04:24:03.346: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.348: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.350: Got instructions of length 16
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.350: Received command SET_KEEP_ALIVE 0
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.351: Keep alive toggled: 0
(process:17641): libfprint-virtual_device_connection-DEBUG: 04:24:03.355: Got a new connection!
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.357: Got instructions of length 19
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.358: Received command SET_ENROLL_STAGES 5
(process:17641): libfprint-device-DEBUG: 04:24:03.360: Device reported close completion
(process:17641): libfprint-device-DEBUG: 04:24:03.361: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17641): libfprint-device-DEBUG: 04:24:03.361: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
Enroll done
ok
(process:17641): libfprint-virtual_device_storage-DEBUG: 04:24:03.364: 38977942962458: ../libfprint/drivers/virtual-device-storage.c:253
(process:17641): libfprint-virtual_device-DEBUG: 04:24:03.364: 38977942962600: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.257s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:280: DeprecationWarning: FPrint.Device.supports_identify is deprecated
self.assertTrue(self.dev.supports_identify())
==============================================================================
=================================== 77/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_identify_match
start time: 04:24:02
duration: 1.11s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=250 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_identify_match
----------------------------------- stdout -----------------------------------
(process:17634): libfprint-context-DEBUG: 04:24:03.124: Initializing FpContext (libfprint version 1.94.6)
(process:17634): libfprint-context-DEBUG: 04:24:03.185: No driver found for USB device 1D6B:0003
(process:17634): libfprint-context-DEBUG: 04:24:03.185: No driver found for USB device 0BDA:5401
(process:17634): libfprint-context-DEBUG: 04:24:03.185: No driver found for USB device 1D6B:0002
(process:17634): libfprint-context-DEBUG: 04:24:03.185: No driver found for USB device 1D6B:0003
(process:17634): libfprint-context-DEBUG: 04:24:03.185: No driver found for USB device 0624:0249
(process:17634): libfprint-context-DEBUG: 04:24:03.185: No driver found for USB device 0624:0248
(process:17634): libfprint-context-DEBUG: 04:24:03.186: No driver found for USB device 1D6B:0002
(process:17634): libfprint-context-DEBUG: 04:24:03.186: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-9jpr477u/virtual-device-storage.socket
(process:17634): libfprint-context-DEBUG: 04:24:03.187: created
(process:17634): libfprint-device-DEBUG: 04:24:03.204: Device reported probe completion
(process:17634): libfprint-device-DEBUG: 04:24:03.205: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17634): libfprint-device-DEBUG: 04:24:03.205: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:17634): libfprint-virtual_device-DEBUG: 04:24:03.216: 38977942814291: ../libfprint/drivers/virtual-device.c:387
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.217: 38977942815659: ../libfprint/drivers/virtual-device-listener.c:153
(process:17634): libfprint-device-DEBUG: 04:24:03.221: Device reported open completion
(process:17634): libfprint-device-DEBUG: 04:24:03.221: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17634): libfprint-device-DEBUG: 04:24:03.221: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.234: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.236: Got instructions of length 16
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.236: Received command SCAN right-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.247: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.247: Processing command SCAN right-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-device-DEBUG: 04:24:03.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.248: Device reported enroll progress, reported 1 of 5 have been completed
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.249: Sleeping completed
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.250: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.251: Got instructions of length 16
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.251: Received command SCAN right-thumb
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.251: Processing command SCAN right-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.251: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-device-DEBUG: 04:24:03.252: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.252: Device reported enroll progress, reported 2 of 5 have been completed
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.253: Sleeping completed
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.263: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.264: Got instructions of length 16
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.264: Received command SCAN right-thumb
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.264: Processing command SCAN right-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.264: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-device-DEBUG: 04:24:03.265: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.265: Device reported enroll progress, reported 3 of 5 have been completed
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.266: Sleeping completed
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.268: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.269: Got instructions of length 16
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.269: Received command SCAN right-thumb
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.269: Processing command SCAN right-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-device-DEBUG: 04:24:03.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.269: Device reported enroll progress, reported 4 of 5 have been completed
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.274: Sleeping completed
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.276: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.277: Got instructions of length 16
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.278: Received command SCAN right-thumb
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.278: Processing command SCAN right-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.278: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-device-DEBUG: 04:24:03.278: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.278: Device reported enroll progress, reported 5 of 5 have been completed
(process:17634): libfprint-device-DEBUG: 04:24:03.278: Device reported enroll completion
(process:17634): libfprint-device-DEBUG: 04:24:03.279: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17634): libfprint-device-DEBUG: 04:24:03.279: Print for finger FP_FINGER_RIGHT_THUMB enrolled
(process:17634): libfprint-device-DEBUG: 04:24:03.280: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17634): libfprint-device-DEBUG: 04:24:03.280: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.295: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.296: Got instructions of length 15
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.296: Received command SCAN left-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.297: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.298: Processing command SCAN left-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.298: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.298: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-device-DEBUG: 04:24:03.298: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.298: Device reported enroll progress, reported 1 of 5 have been completed
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.299: Sleeping completed
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.300: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.301: Got instructions of length 15
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.301: Received command SCAN left-thumb
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.302: Processing command SCAN left-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.302: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-device-DEBUG: 04:24:03.310: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.310: Device reported enroll progress, reported 2 of 5 have been completed
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.311: Sleeping completed
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.313: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.314: Got instructions of length 15
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.314: Received command SCAN left-thumb
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.314: Processing command SCAN left-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.314: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-device-DEBUG: 04:24:03.315: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.315: Device reported enroll progress, reported 3 of 5 have been completed
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.316: Sleeping completed
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.318: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.319: Got instructions of length 15
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.319: Received command SCAN left-thumb
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.319: Processing command SCAN left-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-device-DEBUG: 04:24:03.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.319: Device reported enroll progress, reported 4 of 5 have been completed
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.321: Sleeping completed
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.330: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.331: Got instructions of length 15
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.332: Received command SCAN left-thumb
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.332: Processing command SCAN left-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.332: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-device-DEBUG: 04:24:03.332: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.332: Device reported enroll progress, reported 5 of 5 have been completed
(process:17634): libfprint-device-DEBUG: 04:24:03.332: Device reported enroll completion
(process:17634): libfprint-device-DEBUG: 04:24:03.332: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17634): libfprint-device-DEBUG: 04:24:03.333: Print for finger FP_FINGER_LEFT_THUMB enrolled
(process:17634): libfprint-device-DEBUG: 04:24:03.334: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17634): libfprint-device-DEBUG: 04:24:03.334: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.337: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.338: Got instructions of length 16
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.338: Received command SCAN right-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.351: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.351: Processing command SCAN right-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.351: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.351: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-virtual_device_storage-DEBUG: 04:24:03.352: Trying to identify print 'right-thumb' against a gallery of 2 prints
(process:17634): libfprint-device-DEBUG: 04:24:03.352: Device reported identify result
(process:17634): libfprint-device-DEBUG: 04:24:03.353: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.353: Device reported identify completion
(process:17634): libfprint-device-DEBUG: 04:24:03.353: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17634): libfprint-device-DEBUG: 04:24:03.354: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17634): libfprint-device-DEBUG: 04:24:03.354: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.356: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.357: Got instructions of length 15
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.357: Received command SCAN left-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.363: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.364: Processing command SCAN left-thumb
(process:17634): libfprint-device-DEBUG: 04:24:03.364: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.365: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17634): libfprint-virtual_device_storage-DEBUG: 04:24:03.366: Trying to identify print 'left-thumb' against a gallery of 2 prints
(process:17634): libfprint-device-DEBUG: 04:24:03.367: Device reported identify result
(process:17634): libfprint-device-DEBUG: 04:24:03.368: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17634): libfprint-device-DEBUG: 04:24:03.368: Device reported identify completion
(process:17634): libfprint-device-DEBUG: 04:24:03.369: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17634): libfprint-device-DEBUG: 04:24:03.369: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17634): libfprint-device-DEBUG: 04:24:03.375: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.378: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.379: Got instructions of length 5
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.380: Received command CONT
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.383: Processing command CONT
(process:17634): libfprint-device-DEBUG: 04:24:03.383: Device reported deletion completion
(process:17634): libfprint-device-DEBUG: 04:24:03.384: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17634): libfprint-device-DEBUG: 04:24:03.385: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.394: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.396: Got instructions of length 16
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.397: Received command SET_KEEP_ALIVE 0
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.397: Keep alive toggled: 0
(process:17634): libfprint-virtual_device_connection-DEBUG: 04:24:03.399: Got a new connection!
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.401: Got instructions of length 19
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.401: Received command SET_ENROLL_STAGES 5
(process:17634): libfprint-device-DEBUG: 04:24:03.404: Device reported close completion
(process:17634): libfprint-device-DEBUG: 04:24:03.405: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17634): libfprint-device-DEBUG: 04:24:03.406: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
Enroll done
Enroll done
ok
(process:17634): libfprint-virtual_device_storage-DEBUG: 04:24:03.417: 38977943015547: ../libfprint/drivers/virtual-device-storage.c:253
(process:17634): libfprint-virtual_device-DEBUG: 04:24:03.418: 38977943016054: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.323s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:280: DeprecationWarning: FPrint.Device.supports_identify is deprecated
self.assertTrue(self.dev.supports_identify())
==============================================================================
=================================== 78/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_identify_missing_print
start time: 04:24:02
duration: 0.96s
result: exit status 0
command: MALLOC_PERTURB_=34 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_identify_missing_print
----------------------------------- stdout -----------------------------------
(process:17638): libfprint-context-DEBUG: 04:24:03.321: Initializing FpContext (libfprint version 1.94.6)
(process:17638): libfprint-context-DEBUG: 04:24:03.380: No driver found for USB device 1D6B:0003
(process:17638): libfprint-context-DEBUG: 04:24:03.380: No driver found for USB device 0BDA:5401
(process:17638): libfprint-context-DEBUG: 04:24:03.381: No driver found for USB device 1D6B:0002
(process:17638): libfprint-context-DEBUG: 04:24:03.381: No driver found for USB device 1D6B:0003
(process:17638): libfprint-context-DEBUG: 04:24:03.381: No driver found for USB device 0624:0249
(process:17638): libfprint-context-DEBUG: 04:24:03.381: No driver found for USB device 0624:0248
(process:17638): libfprint-context-DEBUG: 04:24:03.381: No driver found for USB device 1D6B:0002
(process:17638): libfprint-context-DEBUG: 04:24:03.381: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-8p1xmmma/virtual-device-storage.socket
(process:17638): libfprint-context-DEBUG: 04:24:03.383: created
(process:17638): libfprint-device-DEBUG: 04:24:03.402: Device reported probe completion
(process:17638): libfprint-device-DEBUG: 04:24:03.403: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17638): libfprint-device-DEBUG: 04:24:03.403: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:17638): libfprint-virtual_device-DEBUG: 04:24:03.415: 38977943012746: ../libfprint/drivers/virtual-device.c:387
(process:17638): libfprint-virtual_device_connection-DEBUG: 04:24:03.416: 38977943014148: ../libfprint/drivers/virtual-device-listener.c:153
(process:17638): libfprint-device-DEBUG: 04:24:03.419: Device reported open completion
(process:17638): libfprint-device-DEBUG: 04:24:03.419: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17638): libfprint-device-DEBUG: 04:24:03.420: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17638): libfprint-virtual_device_connection-DEBUG: 04:24:03.433: Got a new connection!
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.435: Got instructions of length 23
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.435: Received command SCAN not-existing-print
(process:17638): libfprint-device-DEBUG: 04:24:03.449: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.449: Processing command SCAN not-existing-print
(process:17638): libfprint-device-DEBUG: 04:24:03.449: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17638): libfprint-device-DEBUG: 04:24:03.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17638): libfprint-virtual_device_storage-DEBUG: 04:24:03.450: Trying to identify print 'not-existing-print' against a gallery of 1 prints
(process:17638): libfprint-device-DEBUG: 04:24:03.450: Device reported identify result
(process:17638): libfprint-device-DEBUG: 04:24:03.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17638): libfprint-device-DEBUG: 04:24:03.451: Device reported identify completion
(process:17638): libfprint-device-DEBUG: 04:24:03.451: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17638): libfprint-device-DEBUG: 04:24:03.451: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17638): libfprint-device-DEBUG: 04:24:03.451: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17638): libfprint-virtual_device_connection-DEBUG: 04:24:03.460: Got a new connection!
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.461: Got instructions of length 5
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.461: Received command CONT
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.467: Processing command CONT
(process:17638): libfprint-device-DEBUG: 04:24:03.467: Device reported deletion completion
(process:17638): libfprint-device-DEBUG: 04:24:03.467: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17638): libfprint-device-DEBUG: 04:24:03.468: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17638): libfprint-virtual_device_connection-DEBUG: 04:24:03.469: Got a new connection!
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.474: Got instructions of length 16
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.474: Received command SET_KEEP_ALIVE 0
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.475: Keep alive toggled: 0
(process:17638): libfprint-virtual_device_connection-DEBUG: 04:24:03.476: Got a new connection!
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.478: Got instructions of length 19
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.478: Received command SET_ENROLL_STAGES 5
(process:17638): libfprint-device-DEBUG: 04:24:03.483: Device reported close completion
(process:17638): libfprint-device-DEBUG: 04:24:03.484: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17638): libfprint-device-DEBUG: 04:24:03.484: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17638): libfprint-virtual_device_storage-DEBUG: 04:24:03.490: 38977943088517: ../libfprint/drivers/virtual-device-storage.c:253
(process:17638): libfprint-virtual_device-DEBUG: 04:24:03.490: 38977943088717: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.191s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:280: DeprecationWarning: FPrint.Device.supports_identify is deprecated
self.assertTrue(self.dev.supports_identify())
==============================================================================
=================================== 79/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_identify_retry
start time: 04:24:02
duration: 0.86s
result: exit status 0
command: G_DEBUG=fatal-warnings MALLOC_PERTURB_=168 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_identify_retry
----------------------------------- stdout -----------------------------------
(process:17643): libfprint-context-DEBUG: 04:24:03.564: Initializing FpContext (libfprint version 1.94.6)
(process:17643): libfprint-context-DEBUG: 04:24:03.615: No driver found for USB device 1D6B:0003
(process:17643): libfprint-context-DEBUG: 04:24:03.615: No driver found for USB device 0BDA:5401
(process:17643): libfprint-context-DEBUG: 04:24:03.615: No driver found for USB device 1D6B:0002
(process:17643): libfprint-context-DEBUG: 04:24:03.616: No driver found for USB device 1D6B:0003
(process:17643): libfprint-context-DEBUG: 04:24:03.616: No driver found for USB device 0624:0249
(process:17643): libfprint-context-DEBUG: 04:24:03.616: No driver found for USB device 0624:0248
(process:17643): libfprint-context-DEBUG: 04:24:03.616: No driver found for USB device 1D6B:0002
(process:17643): libfprint-context-DEBUG: 04:24:03.616: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-oa9mtw82/virtual-device-storage.socket
(process:17643): libfprint-context-DEBUG: 04:24:03.619: created
(process:17643): libfprint-device-DEBUG: 04:24:03.637: Device reported probe completion
(process:17643): libfprint-device-DEBUG: 04:24:03.638: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17643): libfprint-device-DEBUG: 04:24:03.640: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:17643): libfprint-virtual_device-DEBUG: 04:24:03.644: 38977943241925: ../libfprint/drivers/virtual-device.c:387
(process:17643): libfprint-virtual_device_connection-DEBUG: 04:24:03.645: 38977943243264: ../libfprint/drivers/virtual-device-listener.c:153
(process:17643): libfprint-device-DEBUG: 04:24:03.649: Device reported open completion
(process:17643): libfprint-device-DEBUG: 04:24:03.650: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17643): libfprint-device-DEBUG: 04:24:03.650: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17643): libfprint-virtual_device_connection-DEBUG: 04:24:03.658: Got a new connection!
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.660: Got instructions of length 7
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.660: Received command RETRY 1
(process:17643): libfprint-device-DEBUG: 04:24:03.667: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.668: Processing command RETRY 1
(process:17643): libfprint-device-DEBUG: 04:24:03.668: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17643): libfprint-device-DEBUG: 04:24:03.669: Device reported identify result
(process:17643): libfprint-device-DEBUG: 04:24:03.669: Device reported identify completion
(process:17643): libfprint-device-DEBUG: 04:24:03.670: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17643): libfprint-device-DEBUG: 04:24:03.670: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17643): libfprint-device-DEBUG: 04:24:03.671: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17643): libfprint-virtual_device_connection-DEBUG: 04:24:03.675: Got a new connection!
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.677: Got instructions of length 5
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.677: Received command CONT
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.679: Processing command CONT
(process:17643): libfprint-device-DEBUG: 04:24:03.682: Device reported deletion completion
(process:17643): libfprint-device-DEBUG: 04:24:03.682: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17643): libfprint-device-DEBUG: 04:24:03.683: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17643): libfprint-virtual_device_connection-DEBUG: 04:24:03.685: Got a new connection!
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.686: Got instructions of length 16
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.687: Received command SET_KEEP_ALIVE 0
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.687: Keep alive toggled: 0
(process:17643): libfprint-virtual_device_connection-DEBUG: 04:24:03.689: Got a new connection!
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.691: Got instructions of length 19
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.692: Received command SET_ENROLL_STAGES 5
(process:17643): libfprint-device-DEBUG: 04:24:03.694: Device reported close completion
(process:17643): libfprint-device-DEBUG: 04:24:03.695: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17643): libfprint-device-DEBUG: 04:24:03.696: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17643): libfprint-virtual_device_storage-DEBUG: 04:24:03.698: 38977943296215: ../libfprint/drivers/virtual-device-storage.c:253
(process:17643): libfprint-virtual_device-DEBUG: 04:24:03.698: 38977943296705: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.156s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:280: DeprecationWarning: FPrint.Device.supports_identify is deprecated
self.assertTrue(self.dev.supports_identify())
==============================================================================
=================================== 80/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_identify_unsupported
start time: 04:24:03
duration: 0.83s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=60 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_identify_unsupported
----------------------------------- stdout -----------------------------------
(process:17654): libfprint-context-DEBUG: 04:24:04.157: Initializing FpContext (libfprint version 1.94.6)
(process:17654): libfprint-context-DEBUG: 04:24:04.221: No driver found for USB device 1D6B:0003
(process:17654): libfprint-context-DEBUG: 04:24:04.221: No driver found for USB device 0BDA:5401
(process:17654): libfprint-context-DEBUG: 04:24:04.221: No driver found for USB device 1D6B:0002
(process:17654): libfprint-context-DEBUG: 04:24:04.221: No driver found for USB device 1D6B:0003
(process:17654): libfprint-context-DEBUG: 04:24:04.221: No driver found for USB device 0624:0249
(process:17654): libfprint-context-DEBUG: 04:24:04.221: No driver found for USB device 0624:0248
(process:17654): libfprint-context-DEBUG: 04:24:04.222: No driver found for USB device 1D6B:0002
(process:17654): libfprint-context-DEBUG: 04:24:04.223: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-oqw2w1fq/virtual-device-storage.socket
(process:17654): libfprint-context-DEBUG: 04:24:04.225: created
(process:17654): libfprint-device-DEBUG: 04:24:04.237: Device reported probe completion
(process:17654): libfprint-device-DEBUG: 04:24:04.237: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17654): libfprint-device-DEBUG: 04:24:04.238: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:17654): libfprint-virtual_device-DEBUG: 04:24:04.241: 38977943839050: ../libfprint/drivers/virtual-device.c:387
(process:17654): libfprint-virtual_device_connection-DEBUG: 04:24:04.242: 38977943840404: ../libfprint/drivers/virtual-device-listener.c:153
(process:17654): libfprint-device-DEBUG: 04:24:04.245: Device reported open completion
(process:17654): libfprint-device-DEBUG: 04:24:04.246: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17654): libfprint-device-DEBUG: 04:24:04.246: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
skipped 'Device supports identification'
(process:17654): libfprint-virtual_device_connection-DEBUG: 04:24:04.251: Got a new connection!
(process:17654): libfprint-virtual_device-DEBUG: 04:24:04.256: Got instructions of length 5
(process:17654): libfprint-virtual_device-DEBUG: 04:24:04.256: Received command CONT
(process:17654): libfprint-virtual_device-DEBUG: 04:24:04.258: Processing command CONT
(process:17654): libfprint-device-DEBUG: 04:24:04.258: Device reported deletion completion
(process:17654): libfprint-device-DEBUG: 04:24:04.259: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17654): libfprint-device-DEBUG: 04:24:04.259: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17654): libfprint-virtual_device_connection-DEBUG: 04:24:04.261: Got a new connection!
(process:17654): libfprint-virtual_device-DEBUG: 04:24:04.264: Got instructions of length 16
(process:17654): libfprint-virtual_device-DEBUG: 04:24:04.265: Received command SET_KEEP_ALIVE 0
(process:17654): libfprint-virtual_device-DEBUG: 04:24:04.265: Keep alive toggled: 0
(process:17654): libfprint-virtual_device_connection-DEBUG: 04:24:04.267: Got a new connection!
(process:17654): libfprint-virtual_device-DEBUG: 04:24:04.269: Got instructions of length 19
(process:17654): libfprint-virtual_device-DEBUG: 04:24:04.269: Received command SET_ENROLL_STAGES 5
(process:17654): libfprint-device-DEBUG: 04:24:04.271: Device reported close completion
(process:17654): libfprint-device-DEBUG: 04:24:04.272: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17654): libfprint-device-DEBUG: 04:24:04.272: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17654): libfprint-virtual_device_storage-DEBUG: 04:24:04.274: 38977943872318: ../libfprint/drivers/virtual-device-storage.c:253
(process:17654): libfprint-virtual_device-DEBUG: 04:24:04.275: 38977943872810: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.136s
OK (skipped=1)
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:902: DeprecationWarning: FPrint.Device.supports_identify is deprecated
if self.dev.supports_identify():
==============================================================================
=================================== 81/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_list_delete_missing
start time: 04:24:03
duration: 1.10s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=16 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_list_delete_missing
----------------------------------- stdout -----------------------------------
(process:17660): libfprint-context-DEBUG: 04:24:03.986: Initializing FpContext (libfprint version 1.94.6)
(process:17660): libfprint-context-DEBUG: 04:24:04.021: No driver found for USB device 1D6B:0003
(process:17660): libfprint-context-DEBUG: 04:24:04.022: No driver found for USB device 0BDA:5401
(process:17660): libfprint-context-DEBUG: 04:24:04.022: No driver found for USB device 1D6B:0002
(process:17660): libfprint-context-DEBUG: 04:24:04.023: No driver found for USB device 1D6B:0003
(process:17660): libfprint-context-DEBUG: 04:24:04.023: No driver found for USB device 0624:0249
(process:17660): libfprint-context-DEBUG: 04:24:04.024: No driver found for USB device 0624:0248
(process:17660): libfprint-context-DEBUG: 04:24:04.024: No driver found for USB device 1D6B:0002
(process:17660): libfprint-context-DEBUG: 04:24:04.025: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-geebfxol/virtual-device-storage.socket
(process:17660): libfprint-context-DEBUG: 04:24:04.027: created
(process:17660): libfprint-device-DEBUG: 04:24:04.038: Device reported probe completion
(process:17660): libfprint-device-DEBUG: 04:24:04.040: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17660): libfprint-device-DEBUG: 04:24:04.040: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:17660): libfprint-virtual_device-DEBUG: 04:24:04.044: 38977943642539: ../libfprint/drivers/virtual-device.c:387
(process:17660): libfprint-virtual_device_connection-DEBUG: 04:24:04.046: 38977943644292: ../libfprint/drivers/virtual-device-listener.c:153
(process:17660): libfprint-device-DEBUG: 04:24:04.049: Device reported open completion
(process:17660): libfprint-device-DEBUG: 04:24:04.050: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17660): libfprint-device-DEBUG: 04:24:04.051: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17660): libfprint-virtual_device_connection-DEBUG: 04:24:04.056: Got a new connection!
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.058: Got instructions of length 14
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.059: Received command SCAN testprint
(process:17660): libfprint-device-DEBUG: 04:24:04.065: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.066: Processing command SCAN testprint
(process:17660): libfprint-device-DEBUG: 04:24:04.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17660): libfprint-device-DEBUG: 04:24:04.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17660): libfprint-device-DEBUG: 04:24:04.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17660): libfprint-device-DEBUG: 04:24:04.068: Device reported enroll progress, reported 1 of 5 have been completed
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.069: Sleeping completed
(process:17660): libfprint-virtual_device_connection-DEBUG: 04:24:04.071: Got a new connection!
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.072: Got instructions of length 14
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.073: Received command SCAN testprint
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.073: Processing command SCAN testprint
(process:17660): libfprint-device-DEBUG: 04:24:04.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17660): libfprint-device-DEBUG: 04:24:04.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17660): libfprint-device-DEBUG: 04:24:04.075: Device reported enroll progress, reported 2 of 5 have been completed
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.076: Sleeping completed
(process:17660): libfprint-virtual_device_connection-DEBUG: 04:24:04.079: Got a new connection!
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.080: Got instructions of length 14
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.081: Received command SCAN testprint
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.081: Processing command SCAN testprint
(process:17660): libfprint-device-DEBUG: 04:24:04.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17660): libfprint-device-DEBUG: 04:24:04.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17660): libfprint-device-DEBUG: 04:24:04.083: Device reported enroll progress, reported 3 of 5 have been completed
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.084: Sleeping completed
(process:17660): libfprint-virtual_device_connection-DEBUG: 04:24:04.086: Got a new connection!
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.088: Got instructions of length 14
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.088: Received command SCAN testprint
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.089: Processing command SCAN testprint
(process:17660): libfprint-device-DEBUG: 04:24:04.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17660): libfprint-device-DEBUG: 04:24:04.090: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17660): libfprint-device-DEBUG: 04:24:04.090: Device reported enroll progress, reported 4 of 5 have been completed
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.092: Sleeping completed
(process:17660): libfprint-virtual_device_connection-DEBUG: 04:24:04.094: Got a new connection!
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.095: Got instructions of length 14
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.096: Received command SCAN testprint
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.096: Processing command SCAN testprint
(process:17660): libfprint-device-DEBUG: 04:24:04.097: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17660): libfprint-device-DEBUG: 04:24:04.097: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17660): libfprint-device-DEBUG: 04:24:04.098: Device reported enroll progress, reported 5 of 5 have been completed
(process:17660): libfprint-device-DEBUG: 04:24:04.098: Device reported enroll completion
(process:17660): libfprint-device-DEBUG: 04:24:04.099: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17660): libfprint-device-DEBUG: 04:24:04.099: Print for finger FP_FINGER_RIGHT_THUMB enrolled
(process:17660): libfprint-device-DEBUG: 04:24:04.101: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17660): libfprint-device-DEBUG: 04:24:04.101: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17660): libfprint-virtual_device_connection-DEBUG: 04:24:04.108: Got a new connection!
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.110: Got instructions of length 16
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.111: Received command REMOVE testprint
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.113: Processing command REMOVE testprint
(process:17660): libfprint-device-DEBUG: 04:24:04.458: Updated temperature model after 0.36 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
(process:17660): libfprint-virtual_device_storage-DEBUG: 04:24:04.618: Deleting print testprint for user testuser
(process:17660): libfprint-device-DEBUG: 04:24:04.618: Device reported deletion completion
(process:17660): libfprint-device-DEBUG: 04:24:04.619: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(process:17660): libfprint-device-DEBUG: 04:24:04.619: Updated temperature model after 0.16 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17660): libfprint-virtual_device_connection-DEBUG: 04:24:04.622: Got a new connection!
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.623: Got instructions of length 5
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.623: Received command CONT
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.624: Processing command CONT
(process:17660): libfprint-device-DEBUG: 04:24:04.624: Device reported deletion completion
(process:17660): libfprint-device-DEBUG: 04:24:04.625: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17660): libfprint-device-DEBUG: 04:24:04.625: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17660): libfprint-virtual_device_connection-DEBUG: 04:24:04.626: Got a new connection!
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.627: Got instructions of length 16
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.628: Received command SET_KEEP_ALIVE 0
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.628: Keep alive toggled: 0
(process:17660): libfprint-virtual_device_connection-DEBUG: 04:24:04.629: Got a new connection!
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.631: Got instructions of length 19
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.631: Received command SET_ENROLL_STAGES 5
(process:17660): libfprint-device-DEBUG: 04:24:04.632: Device reported close completion
(process:17660): libfprint-device-DEBUG: 04:24:04.633: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17660): libfprint-device-DEBUG: 04:24:04.633: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
Enroll done
ok
(process:17660): libfprint-virtual_device_storage-DEBUG: 04:24:04.635: 38977944233140: ../libfprint/drivers/virtual-device-storage.c:253
(process:17660): libfprint-virtual_device-DEBUG: 04:24:04.635: 38977944233300: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.667s
OK
==============================================================================
=================================== 82/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_list_error
start time: 04:24:04
duration: 0.65s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=89 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_list_error
----------------------------------- stdout -----------------------------------
(process:17674): libfprint-context-DEBUG: 04:24:04.714: Initializing FpContext (libfprint version 1.94.6)
(process:17674): libfprint-context-DEBUG: 04:24:04.746: No driver found for USB device 1D6B:0003
(process:17674): libfprint-context-DEBUG: 04:24:04.747: No driver found for USB device 0BDA:5401
(process:17674): libfprint-context-DEBUG: 04:24:04.747: No driver found for USB device 1D6B:0002
(process:17674): libfprint-context-DEBUG: 04:24:04.747: No driver found for USB device 1D6B:0003
(process:17674): libfprint-context-DEBUG: 04:24:04.747: No driver found for USB device 0624:0249
(process:17674): libfprint-context-DEBUG: 04:24:04.747: No driver found for USB device 0624:0248
(process:17674): libfprint-context-DEBUG: 04:24:04.747: No driver found for USB device 1D6B:0002
(process:17674): libfprint-context-DEBUG: 04:24:04.748: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-kvm6d58b/virtual-device-storage.socket
(process:17674): libfprint-context-DEBUG: 04:24:04.749: created
(process:17674): libfprint-device-DEBUG: 04:24:04.761: Device reported probe completion
(process:17674): libfprint-device-DEBUG: 04:24:04.761: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17674): libfprint-device-DEBUG: 04:24:04.762: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:17674): libfprint-virtual_device-DEBUG: 04:24:04.766: 38977944363925: ../libfprint/drivers/virtual-device.c:387
(process:17674): libfprint-virtual_device_connection-DEBUG: 04:24:04.767: 38977944365328: ../libfprint/drivers/virtual-device-listener.c:153
(process:17674): libfprint-device-DEBUG: 04:24:04.770: Device reported open completion
(process:17674): libfprint-device-DEBUG: 04:24:04.770: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17674): libfprint-device-DEBUG: 04:24:04.771: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17674): libfprint-virtual_device_connection-DEBUG: 04:24:04.774: Got a new connection!
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.775: Got instructions of length 9
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.776: Received command SLEEP 100
(process:17674): libfprint-virtual_device_connection-DEBUG: 04:24:04.779: Got a new connection!
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.781: Got instructions of length 7
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.781: Received command ERROR 4
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.785: Processing command SLEEP 100
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.785: Sleeping 100ms
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.887: Sleeping completed
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.887: Processing command ERROR 4
(process:17674): libfprint-device-DEBUG: 04:24:04.888: Device reported listing completion
(process:17674): libfprint-device-DEBUG: 04:24:04.888: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17674): libfprint-device-DEBUG: 04:24:04.889: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17674): libfprint-virtual_device_connection-DEBUG: 04:24:04.894: Got a new connection!
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.895: Got instructions of length 5
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.896: Received command CONT
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.898: Processing command CONT
(process:17674): libfprint-device-DEBUG: 04:24:04.898: Device reported deletion completion
(process:17674): libfprint-device-DEBUG: 04:24:04.899: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17674): libfprint-device-DEBUG: 04:24:04.899: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17674): libfprint-virtual_device_connection-DEBUG: 04:24:04.901: Got a new connection!
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.902: Got instructions of length 16
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.905: Received command SET_KEEP_ALIVE 0
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.906: Keep alive toggled: 0
(process:17674): libfprint-virtual_device_connection-DEBUG: 04:24:04.908: Got a new connection!
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.909: Got instructions of length 19
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.910: Received command SET_ENROLL_STAGES 5
(process:17674): libfprint-device-DEBUG: 04:24:04.913: Device reported close completion
(process:17674): libfprint-device-DEBUG: 04:24:04.913: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17674): libfprint-device-DEBUG: 04:24:04.914: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
----------------------------------------------------------------------
Ran 1 test in 0.220s
OK
(process:17674): libfprint-virtual_device_storage-DEBUG: 04:24:04.939: 38977944537505: ../libfprint/drivers/virtual-device-storage.c:253
(process:17674): libfprint-virtual_device-DEBUG: 04:24:04.940: 38977944538172: ../libfprint/drivers/virtual-device.c:752
==============================================================================
=================================== 83/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_list_empty
start time: 04:24:03
duration: 1.32s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=100 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_list_empty
----------------------------------- stdout -----------------------------------
(process:17663): libfprint-context-DEBUG: 04:24:04.377: Initializing FpContext (libfprint version 1.94.6)
(process:17663): libfprint-context-DEBUG: 04:24:04.420: No driver found for USB device 1D6B:0003
(process:17663): libfprint-context-DEBUG: 04:24:04.420: No driver found for USB device 0BDA:5401
(process:17663): libfprint-context-DEBUG: 04:24:04.420: No driver found for USB device 1D6B:0002
(process:17663): libfprint-context-DEBUG: 04:24:04.420: No driver found for USB device 1D6B:0003
(process:17663): libfprint-context-DEBUG: 04:24:04.420: No driver found for USB device 0624:0249
(process:17663): libfprint-context-DEBUG: 04:24:04.420: No driver found for USB device 0624:0248
(process:17663): libfprint-context-DEBUG: 04:24:04.421: No driver found for USB device 1D6B:0002
(process:17663): libfprint-context-DEBUG: 04:24:04.421: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-j00bjy3c/virtual-device-storage.socket
(process:17663): libfprint-context-DEBUG: 04:24:04.426: created
(process:17663): libfprint-device-DEBUG: 04:24:04.446: Device reported probe completion
(process:17663): libfprint-device-DEBUG: 04:24:04.447: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17663): libfprint-device-DEBUG: 04:24:04.448: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:17663): libfprint-virtual_device-DEBUG: 04:24:04.456: 38977944054112: ../libfprint/drivers/virtual-device.c:387
(process:17663): libfprint-virtual_device_connection-DEBUG: 04:24:04.458: 38977944055873: ../libfprint/drivers/virtual-device-listener.c:153
(process:17663): libfprint-device-DEBUG: 04:24:04.461: Device reported open completion
(process:17663): libfprint-device-DEBUG: 04:24:04.462: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17663): libfprint-device-DEBUG: 04:24:04.463: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17663): libfprint-device-DEBUG: 04:24:04.966: Device reported listing completion
(process:17663): libfprint-device-DEBUG: 04:24:04.966: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17663): libfprint-device-DEBUG: 04:24:04.966: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17663): libfprint-virtual_device_connection-DEBUG: 04:24:04.969: Got a new connection!
(process:17663): libfprint-virtual_device-DEBUG: 04:24:04.971: Got instructions of length 5
(process:17663): libfprint-virtual_device-DEBUG: 04:24:04.971: Received command CONT
(process:17663): libfprint-virtual_device-DEBUG: 04:24:04.973: Processing command CONT
(process:17663): libfprint-device-DEBUG: 04:24:04.973: Device reported deletion completion
(process:17663): libfprint-device-DEBUG: 04:24:04.973: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17663): libfprint-device-DEBUG: 04:24:04.973: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17663): libfprint-virtual_device_connection-DEBUG: 04:24:04.975: Got a new connection!
(process:17663): libfprint-virtual_device-DEBUG: 04:24:04.976: Got instructions of length 16
(process:17663): libfprint-virtual_device-DEBUG: 04:24:04.976: Received command SET_KEEP_ALIVE 0
(process:17663): libfprint-virtual_device-DEBUG: 04:24:04.976: Keep alive toggled: 0
(process:17663): libfprint-virtual_device_connection-DEBUG: 04:24:04.978: Got a new connection!
(process:17663): libfprint-virtual_device-DEBUG: 04:24:04.979: Got instructions of length 19
(process:17663): libfprint-virtual_device-DEBUG: 04:24:04.980: Received command SET_ENROLL_STAGES 5
(process:17663): libfprint-device-DEBUG: 04:24:04.986: Device reported close completion
(process:17663): libfprint-device-DEBUG: 04:24:04.987: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17663): libfprint-device-DEBUG: 04:24:04.987: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17663): libfprint-virtual_device_storage-DEBUG: 04:24:04.990: 38977944588208: ../libfprint/drivers/virtual-device-storage.c:253
(process:17663): libfprint-virtual_device-DEBUG: 04:24:04.990: 38977944588717: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.635s
OK
==============================================================================
=================================== 84/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_open_error
start time: 04:24:05
duration: 0.55s
result: exit status 0
command: MALLOC_PERTURB_=73 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_open_error
----------------------------------- stdout -----------------------------------
(process:17684): libfprint-context-DEBUG: 04:24:05.385: Initializing FpContext (libfprint version 1.94.6)
(process:17684): libfprint-context-DEBUG: 04:24:05.418: No driver found for USB device 1D6B:0003
(process:17684): libfprint-context-DEBUG: 04:24:05.419: No driver found for USB device 0BDA:5401
(process:17684): libfprint-context-DEBUG: 04:24:05.419: No driver found for USB device 1D6B:0002
(process:17684): libfprint-context-DEBUG: 04:24:05.420: No driver found for USB device 1D6B:0003
(process:17684): libfprint-context-DEBUG: 04:24:05.420: No driver found for USB device 0624:0249
(process:17684): libfprint-context-DEBUG: 04:24:05.421: No driver found for USB device 0624:0248
(process:17684): libfprint-context-DEBUG: 04:24:05.421: No driver found for USB device 1D6B:0002
(process:17684): libfprint-context-DEBUG: 04:24:05.422: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-_d5w323k/virtual-device-storage.socket
(process:17684): libfprint-context-DEBUG: 04:24:05.423: created
(process:17684): libfprint-device-DEBUG: 04:24:05.436: Device reported probe completion
(process:17684): libfprint-device-DEBUG: 04:24:05.437: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17684): libfprint-device-DEBUG: 04:24:05.437: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:17684): libfprint-virtual_device-DEBUG: 04:24:05.441: 38977945039591: ../libfprint/drivers/virtual-device.c:387
(process:17684): libfprint-virtual_device_connection-DEBUG: 04:24:05.443: 38977945041383: ../libfprint/drivers/virtual-device-listener.c:153
(process:17684): libfprint-device-DEBUG: 04:24:05.447: Device reported open completion
(process:17684): libfprint-device-DEBUG: 04:24:05.447: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17684): libfprint-device-DEBUG: 04:24:05.448: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17684): libfprint-virtual_device_connection-DEBUG: 04:24:05.451: Got a new connection!
(process:17684): libfprint-virtual_device-DEBUG: 04:24:05.453: Got instructions of length 16
(process:17684): libfprint-virtual_device-DEBUG: 04:24:05.454: Received command IGNORED_COMMAND
(process:17684): libfprint-virtual_device_connection-DEBUG: 04:24:05.457: Got a new connection!
(process:17684): libfprint-virtual_device-DEBUG: 04:24:05.459: Got instructions of length 7
(process:17684): libfprint-virtual_device-DEBUG: 04:24:05.459: Received command ERROR 5
(process:17684): libfprint-virtual_device-DEBUG: 04:24:05.462: Processing command IGNORED_COMMAND
(process:17684): libfprint-device-DEBUG: 04:24:05.463: Device reported close completion
(process:17684): libfprint-device-DEBUG: 04:24:05.464: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17684): libfprint-device-DEBUG: 04:24:05.464: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17684): libfprint-virtual_device-DEBUG: 04:24:05.470: 38977945068400: ../libfprint/drivers/virtual-device.c:387
(process:17684): libfprint-virtual_device-DEBUG: 04:24:05.471: Processing command ERROR 5
(process:17684): libfprint-device-DEBUG: 04:24:05.471: Device reported open completion
(process:17684): libfprint-device-DEBUG: 04:24:05.472: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17684): libfprint-device-DEBUG: 04:24:05.473: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17684): libfprint-virtual_device_storage-DEBUG: 04:24:05.476: 38977945074093: ../libfprint/drivers/virtual-device-storage.c:253
(process:17684): libfprint-virtual_device-DEBUG: 04:24:05.476: 38977945074612: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.107s
OK
==============================================================================
=================================== 85/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_list_delete
start time: 04:24:03
duration: 2.36s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=233 NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_list_delete
----------------------------------- stdout -----------------------------------
(process:17656): libfprint-context-DEBUG: 04:24:04.133: Initializing FpContext (libfprint version 1.94.6)
(process:17656): libfprint-context-DEBUG: 04:24:04.166: No driver found for USB device 1D6B:0003
(process:17656): libfprint-context-DEBUG: 04:24:04.167: No driver found for USB device 0BDA:5401
(process:17656): libfprint-context-DEBUG: 04:24:04.167: No driver found for USB device 1D6B:0002
(process:17656): libfprint-context-DEBUG: 04:24:04.168: No driver found for USB device 1D6B:0003
(process:17656): libfprint-context-DEBUG: 04:24:04.168: No driver found for USB device 0624:0249
(process:17656): libfprint-context-DEBUG: 04:24:04.169: No driver found for USB device 0624:0248
(process:17656): libfprint-context-DEBUG: 04:24:04.169: No driver found for USB device 1D6B:0002
(process:17656): libfprint-context-DEBUG: 04:24:04.169: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-2908le0i/virtual-device-storage.socket
(process:17656): libfprint-context-DEBUG: 04:24:04.171: created
(process:17656): libfprint-device-DEBUG: 04:24:04.184: Device reported probe completion
(process:17656): libfprint-device-DEBUG: 04:24:04.185: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17656): libfprint-device-DEBUG: 04:24:04.186: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:17656): libfprint-virtual_device-DEBUG: 04:24:04.190: 38977943787875: ../libfprint/drivers/virtual-device.c:387
(process:17656): libfprint-virtual_device_connection-DEBUG: 04:24:04.191: 38977943789595: ../libfprint/drivers/virtual-device-listener.c:153
(process:17656): libfprint-device-DEBUG: 04:24:04.195: Device reported open completion
(process:17656): libfprint-device-DEBUG: 04:24:04.195: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17656): libfprint-device-DEBUG: 04:24:04.196: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17656): libfprint-virtual_device_connection-DEBUG: 04:24:04.201: Got a new connection!
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.203: Got instructions of length 14
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.204: Received command SCAN testprint
(process:17656): libfprint-device-DEBUG: 04:24:04.211: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.211: Processing command SCAN testprint
(process:17656): libfprint-device-DEBUG: 04:24:04.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17656): libfprint-device-DEBUG: 04:24:04.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17656): libfprint-device-DEBUG: 04:24:04.213: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17656): libfprint-device-DEBUG: 04:24:04.213: Device reported enroll progress, reported 1 of 5 have been completed
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.215: Sleeping completed
(process:17656): libfprint-virtual_device_connection-DEBUG: 04:24:04.216: Got a new connection!
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.218: Got instructions of length 14
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.218: Received command SCAN testprint
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.219: Processing command SCAN testprint
(process:17656): libfprint-device-DEBUG: 04:24:04.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17656): libfprint-device-DEBUG: 04:24:04.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17656): libfprint-device-DEBUG: 04:24:04.220: Device reported enroll progress, reported 2 of 5 have been completed
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.223: Sleeping completed
(process:17656): libfprint-virtual_device_connection-DEBUG: 04:24:04.225: Got a new connection!
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.226: Got instructions of length 14
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.227: Received command SCAN testprint
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.227: Processing command SCAN testprint
(process:17656): libfprint-device-DEBUG: 04:24:04.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17656): libfprint-device-DEBUG: 04:24:04.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17656): libfprint-device-DEBUG: 04:24:04.229: Device reported enroll progress, reported 3 of 5 have been completed
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.231: Sleeping completed
(process:17656): libfprint-virtual_device_connection-DEBUG: 04:24:04.233: Got a new connection!
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.234: Got instructions of length 14
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.235: Received command SCAN testprint
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.235: Processing command SCAN testprint
(process:17656): libfprint-device-DEBUG: 04:24:04.236: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17656): libfprint-device-DEBUG: 04:24:04.236: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17656): libfprint-device-DEBUG: 04:24:04.237: Device reported enroll progress, reported 4 of 5 have been completed
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.239: Sleeping completed
(process:17656): libfprint-virtual_device_connection-DEBUG: 04:24:04.242: Got a new connection!
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.244: Got instructions of length 14
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.244: Received command SCAN testprint
(process:17656): libfprint-virtual_device-DEBUG: 04:24:04.244: Processing command SCAN testprint
(process:17656): libfprint-device-DEBUG: 04:24:04.245: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17656): libfprint-device-DEBUG: 04:24:04.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17656): libfprint-device-DEBUG: 04:24:04.247: Device reported enroll progress, reported 5 of 5 have been completed
(process:17656): libfprint-device-DEBUG: 04:24:04.247: Device reported enroll completion
(process:17656): libfprint-device-DEBUG: 04:24:04.248: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17656): libfprint-device-DEBUG: 04:24:04.249: Print for finger FP_FINGER_RIGHT_THUMB enrolled
(process:17656): libfprint-device-DEBUG: 04:24:04.250: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17656): libfprint-device-DEBUG: 04:24:04.251: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17656): libfprint-device-DEBUG: 04:24:04.638: Updated temperature model after 0.39 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
(process:17656): libfprint-device-DEBUG: 04:24:04.762: Device reported listing completion
(process:17656): libfprint-device-DEBUG: 04:24:04.763: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17656): libfprint-device-DEBUG: 04:24:04.763: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17656): libfprint-virtual_device_storage-DEBUG: 04:24:05.266: Deleting print testprint for user testuser
(process:17656): libfprint-device-DEBUG: 04:24:05.266: Device reported deletion completion
(process:17656): libfprint-device-DEBUG: 04:24:05.266: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(process:17656): libfprint-device-DEBUG: 04:24:05.267: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17656): libfprint-device-DEBUG: 04:24:05.768: Device reported listing completion
(process:17656): libfprint-device-DEBUG: 04:24:05.768: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17656): libfprint-device-DEBUG: 04:24:05.768: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17656): libfprint-virtual_device_connection-DEBUG: 04:24:05.770: Got a new connection!
(process:17656): libfprint-virtual_device-DEBUG: 04:24:05.771: Got instructions of length 5
(process:17656): libfprint-virtual_device-DEBUG: 04:24:05.771: Received command CONT
(process:17656): libfprint-virtual_device-DEBUG: 04:24:05.773: Processing command CONT
(process:17656): libfprint-device-DEBUG: 04:24:05.773: Device reported deletion completion
(process:17656): libfprint-device-DEBUG: 04:24:05.773: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17656): libfprint-device-DEBUG: 04:24:05.773: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17656): libfprint-virtual_device_connection-DEBUG: 04:24:05.775: Got a new connection!
(process:17656): libfprint-virtual_device-DEBUG: 04:24:05.776: Got instructions of length 16
(process:17656): libfprint-virtual_device-DEBUG: 04:24:05.776: Received command SET_KEEP_ALIVE 0
(process:17656): libfprint-virtual_device-DEBUG: 04:24:05.776: Keep alive toggled: 0
(process:17656): libfprint-virtual_device_connection-DEBUG: 04:24:05.779: Got a new connection!
(process:17656): libfprint-virtual_device-DEBUG: 04:24:05.780: Got instructions of length 19
(process:17656): libfprint-virtual_device-DEBUG: 04:24:05.781: Received command SET_ENROLL_STAGES 5
(process:17656): libfprint-device-DEBUG: 04:24:05.782: Device reported close completion
(process:17656): libfprint-device-DEBUG: 04:24:05.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17656): libfprint-device-DEBUG: 04:24:05.799: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
Enroll done
<FPrint.Print object at 0xf71466e8 (FpPrint at 0x14de100)>
blub 'testprint' <class 'gi.overrides.GLib.Variant'>
ok
(process:17656): libfprint-virtual_device_storage-DEBUG: 04:24:05.801: 38977945398895: ../libfprint/drivers/virtual-device-storage.c:253
(process:17656): libfprint-virtual_device-DEBUG: 04:24:05.801: 38977945399032: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 1.679s
OK
==============================================================================
=================================== 86/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_list_populated
start time: 04:24:04
duration: 1.26s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=159 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_list_populated
----------------------------------- stdout -----------------------------------
(process:17679): libfprint-context-DEBUG: 04:24:05.147: Initializing FpContext (libfprint version 1.94.6)
(process:17679): libfprint-context-DEBUG: 04:24:05.181: No driver found for USB device 1D6B:0003
(process:17679): libfprint-context-DEBUG: 04:24:05.182: No driver found for USB device 0BDA:5401
(process:17679): libfprint-context-DEBUG: 04:24:05.183: No driver found for USB device 1D6B:0002
(process:17679): libfprint-context-DEBUG: 04:24:05.183: No driver found for USB device 1D6B:0003
(process:17679): libfprint-context-DEBUG: 04:24:05.183: No driver found for USB device 0624:0249
(process:17679): libfprint-context-DEBUG: 04:24:05.184: No driver found for USB device 0624:0248
(process:17679): libfprint-context-DEBUG: 04:24:05.184: No driver found for USB device 1D6B:0002
(process:17679): libfprint-context-DEBUG: 04:24:05.185: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-nitvudu2/virtual-device-storage.socket
(process:17679): libfprint-context-DEBUG: 04:24:05.187: created
(process:17679): libfprint-device-DEBUG: 04:24:05.201: Device reported probe completion
(process:17679): libfprint-device-DEBUG: 04:24:05.202: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17679): libfprint-device-DEBUG: 04:24:05.203: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:17679): libfprint-virtual_device-DEBUG: 04:24:05.207: 38977944805137: ../libfprint/drivers/virtual-device.c:387
(process:17679): libfprint-virtual_device_connection-DEBUG: 04:24:05.209: 38977944806843: ../libfprint/drivers/virtual-device-listener.c:153
(process:17679): libfprint-device-DEBUG: 04:24:05.212: Device reported open completion
(process:17679): libfprint-device-DEBUG: 04:24:05.213: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17679): libfprint-device-DEBUG: 04:24:05.213: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17679): libfprint-virtual_device_connection-DEBUG: 04:24:05.217: Got a new connection!
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.223: Got instructions of length 9
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.224: Received command INSERT p1
(process:17679): libfprint-virtual_device_connection-DEBUG: 04:24:05.228: Got a new connection!
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.229: Got instructions of length 7
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.242: Received command SCAN p2
(process:17679): libfprint-device-DEBUG: 04:24:05.248: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.249: Processing command INSERT p1
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.250: Processing command SCAN p2
(process:17679): libfprint-device-DEBUG: 04:24:05.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17679): libfprint-device-DEBUG: 04:24:05.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17679): libfprint-device-DEBUG: 04:24:05.251: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17679): libfprint-device-DEBUG: 04:24:05.251: Device reported enroll progress, reported 1 of 5 have been completed
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.252: Sleeping completed
(process:17679): libfprint-virtual_device_connection-DEBUG: 04:24:05.258: Got a new connection!
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.260: Got instructions of length 7
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.260: Received command SCAN p2
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.261: Processing command SCAN p2
(process:17679): libfprint-device-DEBUG: 04:24:05.261: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17679): libfprint-device-DEBUG: 04:24:05.262: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17679): libfprint-device-DEBUG: 04:24:05.262: Device reported enroll progress, reported 2 of 5 have been completed
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.263: Sleeping completed
(process:17679): libfprint-virtual_device_connection-DEBUG: 04:24:05.265: Got a new connection!
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.271: Got instructions of length 7
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.272: Received command SCAN p2
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.272: Processing command SCAN p2
(process:17679): libfprint-device-DEBUG: 04:24:05.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17679): libfprint-device-DEBUG: 04:24:05.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17679): libfprint-device-DEBUG: 04:24:05.274: Device reported enroll progress, reported 3 of 5 have been completed
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.275: Sleeping completed
(process:17679): libfprint-virtual_device_connection-DEBUG: 04:24:05.277: Got a new connection!
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.287: Got instructions of length 7
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.287: Received command SCAN p2
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.288: Processing command SCAN p2
(process:17679): libfprint-device-DEBUG: 04:24:05.288: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17679): libfprint-device-DEBUG: 04:24:05.289: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17679): libfprint-device-DEBUG: 04:24:05.289: Device reported enroll progress, reported 4 of 5 have been completed
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.290: Sleeping completed
(process:17679): libfprint-virtual_device_connection-DEBUG: 04:24:05.292: Got a new connection!
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.294: Got instructions of length 7
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.294: Received command SCAN p2
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.295: Processing command SCAN p2
(process:17679): libfprint-device-DEBUG: 04:24:05.295: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17679): libfprint-device-DEBUG: 04:24:05.296: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17679): libfprint-device-DEBUG: 04:24:05.296: Device reported enroll progress, reported 5 of 5 have been completed
(process:17679): libfprint-device-DEBUG: 04:24:05.297: Device reported enroll completion
(process:17679): libfprint-device-DEBUG: 04:24:05.297: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17679): libfprint-device-DEBUG: 04:24:05.297: Print for finger FP_FINGER_LEFT_LITTLE enrolled
(process:17679): libfprint-device-DEBUG: 04:24:05.303: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17679): libfprint-device-DEBUG: 04:24:05.304: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17679): libfprint-device-DEBUG: 04:24:05.794: Updated temperature model after 0.49 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
(process:17679): libfprint-device-DEBUG: 04:24:05.810: Device reported listing completion
(process:17679): libfprint-device-DEBUG: 04:24:05.811: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17679): libfprint-device-DEBUG: 04:24:05.812: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17679): libfprint-virtual_device_connection-DEBUG: 04:24:05.819: Got a new connection!
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.821: Got instructions of length 5
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.821: Received command CONT
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.823: Processing command CONT
(process:17679): libfprint-device-DEBUG: 04:24:05.823: Device reported deletion completion
(process:17679): libfprint-device-DEBUG: 04:24:05.824: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17679): libfprint-device-DEBUG: 04:24:05.824: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17679): libfprint-virtual_device_connection-DEBUG: 04:24:05.830: Got a new connection!
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.831: Got instructions of length 16
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.832: Received command SET_KEEP_ALIVE 0
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.832: Keep alive toggled: 0
(process:17679): libfprint-virtual_device_connection-DEBUG: 04:24:05.834: Got a new connection!
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.835: Got instructions of length 19
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.835: Received command SET_ENROLL_STAGES 5
(process:17679): libfprint-device-DEBUG: 04:24:05.837: Device reported close completion
(process:17679): libfprint-device-DEBUG: 04:24:05.838: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17679): libfprint-device-DEBUG: 04:24:05.846: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
Enroll done
ok
(process:17679): libfprint-virtual_device_storage-DEBUG: 04:24:05.849: 38977945446967: ../libfprint/drivers/virtual-device-storage.c:253
(process:17679): libfprint-virtual_device-DEBUG: 04:24:05.849: 38977945447446: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.720s
OK
==============================================================================
=================================== 87/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_open_error_with_keep_alive
start time: 04:24:05
duration: 0.92s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=133 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_open_error_with_keep_alive
----------------------------------- stdout -----------------------------------
(process:17686): libfprint-context-DEBUG: 04:24:05.800: Initializing FpContext (libfprint version 1.94.6)
(process:17686): libfprint-context-DEBUG: 04:24:05.833: No driver found for USB device 1D6B:0003
(process:17686): libfprint-context-DEBUG: 04:24:05.833: No driver found for USB device 0BDA:5401
(process:17686): libfprint-context-DEBUG: 04:24:05.834: No driver found for USB device 1D6B:0002
(process:17686): libfprint-context-DEBUG: 04:24:05.834: No driver found for USB device 1D6B:0003
(process:17686): libfprint-context-DEBUG: 04:24:05.835: No driver found for USB device 0624:0249
(process:17686): libfprint-context-DEBUG: 04:24:05.836: No driver found for USB device 0624:0248
(process:17686): libfprint-context-DEBUG: 04:24:05.836: No driver found for USB device 1D6B:0002
(process:17686): libfprint-context-DEBUG: 04:24:05.837: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-4em0a_0x/virtual-device-storage.socket
(process:17686): libfprint-context-DEBUG: 04:24:05.840: created
(process:17686): libfprint-device-DEBUG: 04:24:05.853: Device reported probe completion
(process:17686): libfprint-device-DEBUG: 04:24:05.853: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17686): libfprint-device-DEBUG: 04:24:05.854: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:17686): libfprint-virtual_device-DEBUG: 04:24:05.858: 38977945456416: ../libfprint/drivers/virtual-device.c:387
(process:17686): libfprint-virtual_device_connection-DEBUG: 04:24:05.860: 38977945458386: ../libfprint/drivers/virtual-device-listener.c:153
(process:17686): libfprint-device-DEBUG: 04:24:05.864: Device reported open completion
(process:17686): libfprint-device-DEBUG: 04:24:05.864: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17686): libfprint-device-DEBUG: 04:24:05.865: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17686): libfprint-virtual_device_connection-DEBUG: 04:24:05.868: Got a new connection!
(process:17686): libfprint-virtual_device-DEBUG: 04:24:05.870: Got instructions of length 16
(process:17686): libfprint-virtual_device-DEBUG: 04:24:05.871: Received command SET_KEEP_ALIVE 1
(process:17686): libfprint-virtual_device-DEBUG: 04:24:05.871: Keep alive toggled: 1
(process:17686): libfprint-device-DEBUG: 04:24:05.873: Device reported close completion
(process:17686): libfprint-device-DEBUG: 04:24:05.874: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17686): libfprint-device-DEBUG: 04:24:05.874: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17686): libfprint-virtual_device_connection-DEBUG: 04:24:05.877: Got a new connection!
(process:17686): libfprint-virtual_device-DEBUG: 04:24:05.879: Got instructions of length 7
(process:17686): libfprint-virtual_device-DEBUG: 04:24:05.880: Received command ERROR 5
(process:17686): libfprint-virtual_device-DEBUG: 04:24:05.881: 38977945479319: ../libfprint/drivers/virtual-device.c:387
(process:17686): libfprint-virtual_device-DEBUG: 04:24:05.882: Processing command ERROR 5
(process:17686): libfprint-device-DEBUG: 04:24:05.882: Device reported open completion
(process:17686): libfprint-device-DEBUG: 04:24:05.883: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17686): libfprint-device-DEBUG: 04:24:05.883: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17686): libfprint-virtual_device_storage-DEBUG: 04:24:05.886: 38977945484277: ../libfprint/drivers/virtual-device-storage.c:253
(process:17686): libfprint-virtual_device-DEBUG: 04:24:05.887: 38977945484787: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.111s
OK
==============================================================================
=================================== 88/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_quick_enroll
start time: 04:24:05
duration: 0.63s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=240 /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_quick_enroll
----------------------------------- stdout -----------------------------------
(process:17694): libfprint-context-DEBUG: 04:24:06.015: Initializing FpContext (libfprint version 1.94.6)
(process:17694): libfprint-context-DEBUG: 04:24:06.052: No driver found for USB device 1D6B:0003
(process:17694): libfprint-context-DEBUG: 04:24:06.052: No driver found for USB device 0BDA:5401
(process:17694): libfprint-context-DEBUG: 04:24:06.052: No driver found for USB device 1D6B:0002
(process:17694): libfprint-context-DEBUG: 04:24:06.053: No driver found for USB device 1D6B:0003
(process:17694): libfprint-context-DEBUG: 04:24:06.053: No driver found for USB device 0624:0249
(process:17694): libfprint-context-DEBUG: 04:24:06.053: No driver found for USB device 0624:0248
(process:17694): libfprint-context-DEBUG: 04:24:06.053: No driver found for USB device 1D6B:0002
(process:17694): libfprint-context-DEBUG: 04:24:06.053: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-9s2tvduc/virtual-device-storage.socket
(process:17694): libfprint-context-DEBUG: 04:24:06.055: created
(process:17694): libfprint-device-DEBUG: 04:24:06.067: Device reported probe completion
(process:17694): libfprint-device-DEBUG: 04:24:06.067: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17694): libfprint-device-DEBUG: 04:24:06.068: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:17694): libfprint-virtual_device-DEBUG: 04:24:06.071: 38977945669027: ../libfprint/drivers/virtual-device.c:387
(process:17694): libfprint-virtual_device_connection-DEBUG: 04:24:06.072: 38977945670349: ../libfprint/drivers/virtual-device-listener.c:153
(process:17694): libfprint-device-DEBUG: 04:24:06.075: Device reported open completion
(process:17694): libfprint-device-DEBUG: 04:24:06.075: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17694): libfprint-device-DEBUG: 04:24:06.076: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17694): libfprint-virtual_device_connection-DEBUG: 04:24:06.078: Got a new connection!
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.080: Got instructions of length 19
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.080: Received command SET_ENROLL_STAGES 1
(process:17694): libfprint-virtual_device_connection-DEBUG: 04:24:06.084: Got a new connection!
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.085: Got instructions of length 14
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.085: Received command SCAN testprint
(process:17694): libfprint-device-DEBUG: 04:24:06.091: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.092: Processing command SCAN testprint
(process:17694): libfprint-device-DEBUG: 04:24:06.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17694): libfprint-device-DEBUG: 04:24:06.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17694): libfprint-device-DEBUG: 04:24:06.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17694): libfprint-device-DEBUG: 04:24:06.092: Device reported enroll progress, reported 1 of 1 have been completed
(process:17694): libfprint-device-DEBUG: 04:24:06.093: Device reported enroll completion
(process:17694): libfprint-device-DEBUG: 04:24:06.093: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17694): libfprint-device-DEBUG: 04:24:06.093: Print for finger FP_FINGER_LEFT_LITTLE enrolled
(process:17694): libfprint-device-DEBUG: 04:24:06.093: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17694): libfprint-device-DEBUG: 04:24:06.094: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17694): libfprint-virtual_device_connection-DEBUG: 04:24:06.100: Got a new connection!
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.101: Got instructions of length 5
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.101: Received command CONT
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.103: Processing command CONT
(process:17694): libfprint-device-DEBUG: 04:24:06.103: Device reported deletion completion
(process:17694): libfprint-device-DEBUG: 04:24:06.103: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17694): libfprint-device-DEBUG: 04:24:06.103: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17694): libfprint-virtual_device_connection-DEBUG: 04:24:06.105: Got a new connection!
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.106: Got instructions of length 16
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.106: Received command SET_KEEP_ALIVE 0
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.106: Keep alive toggled: 0
(process:17694): libfprint-virtual_device_connection-DEBUG: 04:24:06.108: Got a new connection!
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.109: Got instructions of length 19
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.109: Received command SET_ENROLL_STAGES 5
(process:17694): libfprint-device-DEBUG: 04:24:06.110: Device reported close completion
(process:17694): libfprint-device-DEBUG: 04:24:06.111: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17694): libfprint-device-DEBUG: 04:24:06.111: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
Enroll done
ok
(process:17694): libfprint-virtual_device_storage-DEBUG: 04:24:06.113: 38977945711321: ../libfprint/drivers/virtual-device-storage.c:253
(process:17694): libfprint-virtual_device-DEBUG: 04:24:06.113: 38977945711463: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.112s
OK
==============================================================================
=================================== 89/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceUnplugging / VirtualDeviceUnplugging.test_device_unplug
start time: 04:24:05
duration: 0.74s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=178 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceUnplugging.test_device_unplug
----------------------------------- stdout -----------------------------------
test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:17701): libfprint-context-DEBUG: 04:24:06.547: Initializing FpContext (libfprint version 1.94.6)
(process:17701): libfprint-context-DEBUG: 04:24:06.599: No driver found for USB device 1D6B:0003
(process:17701): libfprint-context-DEBUG: 04:24:06.599: No driver found for USB device 0BDA:5401
(process:17701): libfprint-context-DEBUG: 04:24:06.599: No driver found for USB device 1D6B:0002
(process:17701): libfprint-context-DEBUG: 04:24:06.599: No driver found for USB device 1D6B:0003
(process:17701): libfprint-context-DEBUG: 04:24:06.599: No driver found for USB device 0624:0249
(process:17701): libfprint-context-DEBUG: 04:24:06.599: No driver found for USB device 0624:0248
(process:17701): libfprint-context-DEBUG: 04:24:06.600: No driver found for USB device 1D6B:0002
(process:17701): libfprint-context-DEBUG: 04:24:06.600: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-3cxk4vwe/virtual-device.socket
(process:17701): libfprint-context-DEBUG: 04:24:06.601: created
(process:17701): libfprint-device-DEBUG: 04:24:06.614: Device reported probe completion
(process:17701): libfprint-device-DEBUG: 04:24:06.615: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17701): libfprint-device-DEBUG: 04:24:06.616: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17701): libfprint-virtual_device-DEBUG: 04:24:06.619: 38977946216971: ../libfprint/drivers/virtual-device.c:387
(process:17701): libfprint-virtual_device_connection-DEBUG: 04:24:06.620: 38977946218723: ../libfprint/drivers/virtual-device-listener.c:153
(process:17701): libfprint-device-DEBUG: 04:24:06.626: Device reported open completion
(process:17701): libfprint-device-DEBUG: 04:24:06.627: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17701): libfprint-device-DEBUG: 04:24:06.628: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17701): libfprint-virtual_device_connection-DEBUG: 04:24:06.632: Got a new connection!
(process:17701): libfprint-virtual_device-DEBUG: 04:24:06.634: Got instructions of length 7
(process:17701): libfprint-virtual_device-DEBUG: 04:24:06.634: Received command UNPLUG
(process:17701): libfprint-device-DEBUG: 04:24:06.638: Device reported close completion
(process:17701): libfprint-device-DEBUG: 04:24:06.639: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17701): libfprint-device-DEBUG: 04:24:06.639: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17701): libfprint-virtual_device-DEBUG: 04:24:06.644: 38977946241905: ../libfprint/drivers/virtual-device.c:752
ok
----------------------------------------------------------------------
Ran 1 test in 0.131s
OK
==============================================================================
=================================== 90/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceStorage / VirtualDeviceStorage.test_verify_missing_print
start time: 04:24:05
duration: 0.83s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=231 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceStorage.test_verify_missing_print
----------------------------------- stdout -----------------------------------
(process:17699): libfprint-context-DEBUG: 04:24:06.567: Initializing FpContext (libfprint version 1.94.6)
(process:17699): libfprint-context-DEBUG: 04:24:06.621: No driver found for USB device 1D6B:0003
(process:17699): libfprint-context-DEBUG: 04:24:06.622: No driver found for USB device 0BDA:5401
(process:17699): libfprint-context-DEBUG: 04:24:06.622: No driver found for USB device 1D6B:0002
(process:17699): libfprint-context-DEBUG: 04:24:06.622: No driver found for USB device 1D6B:0003
(process:17699): libfprint-context-DEBUG: 04:24:06.622: No driver found for USB device 0624:0249
(process:17699): libfprint-context-DEBUG: 04:24:06.622: No driver found for USB device 0624:0248
(process:17699): libfprint-context-DEBUG: 04:24:06.623: No driver found for USB device 1D6B:0002
(process:17699): libfprint-context-DEBUG: 04:24:06.623: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-zloazz0a/virtual-device-storage.socket
(process:17699): libfprint-context-DEBUG: 04:24:06.624: created
(process:17699): libfprint-device-DEBUG: 04:24:06.636: Device reported probe completion
(process:17699): libfprint-device-DEBUG: 04:24:06.636: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17699): libfprint-device-DEBUG: 04:24:06.637: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:17699): libfprint-virtual_device-DEBUG: 04:24:06.640: 38977946238068: ../libfprint/drivers/virtual-device.c:387
(process:17699): libfprint-virtual_device_connection-DEBUG: 04:24:06.641: 38977946239399: ../libfprint/drivers/virtual-device-listener.c:153
(process:17699): libfprint-device-DEBUG: 04:24:06.644: Device reported open completion
(process:17699): libfprint-device-DEBUG: 04:24:06.645: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17699): libfprint-device-DEBUG: 04:24:06.645: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17699): libfprint-virtual_device_connection-DEBUG: 04:24:06.650: Got a new connection!
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.652: Got instructions of length 23
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.653: Received command SCAN not-existing-print
(process:17699): libfprint-device-DEBUG: 04:24:06.657: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.657: Processing command SCAN not-existing-print
(process:17699): libfprint-device-DEBUG: 04:24:06.657: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17699): libfprint-device-DEBUG: 04:24:06.658: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.658: Virtual device scanned print not-existing-print
(process:17699): libfprint-device-DEBUG: 04:24:06.658: Device reported verify result
(process:17699): libfprint-device-DEBUG: 04:24:06.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17699): libfprint-device-DEBUG: 04:24:06.659: Device reported verify completion
(process:17699): libfprint-device-DEBUG: 04:24:06.660: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17699): libfprint-device-DEBUG: 04:24:06.661: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17699): libfprint-device-DEBUG: 04:24:06.661: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17699): libfprint-virtual_device_connection-DEBUG: 04:24:06.666: Got a new connection!
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.668: Got instructions of length 5
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.668: Received command CONT
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.670: Processing command CONT
(process:17699): libfprint-device-DEBUG: 04:24:06.671: Device reported deletion completion
(process:17699): libfprint-device-DEBUG: 04:24:06.671: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17699): libfprint-device-DEBUG: 04:24:06.672: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
(process:17699): libfprint-virtual_device_connection-DEBUG: 04:24:06.673: Got a new connection!
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.675: Got instructions of length 16
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.675: Received command SET_KEEP_ALIVE 0
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.676: Keep alive toggled: 0
(process:17699): libfprint-virtual_device_connection-DEBUG: 04:24:06.678: Got a new connection!
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.679: Got instructions of length 19
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.680: Received command SET_ENROLL_STAGES 5
(process:17699): libfprint-device-DEBUG: 04:24:06.681: Device reported close completion
(process:17699): libfprint-device-DEBUG: 04:24:06.682: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17699): libfprint-device-DEBUG: 04:24:06.683: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok
(process:17699): libfprint-virtual_device_storage-DEBUG: 04:24:06.686: 38977946283871: ../libfprint/drivers/virtual-device-storage.c:253
(process:17699): libfprint-virtual_device-DEBUG: 04:24:06.686: 38977946284544: ../libfprint/drivers/virtual-device.c:752
----------------------------------------------------------------------
Ran 1 test in 0.142s
OK
==============================================================================
=================================== 91/116 ===================================
test: libfprint:virtual-driver+virtual-device+VirtualDeviceUnplugging / VirtualDeviceUnplugging.test_device_unplug_during_verify
start time: 04:24:06
duration: 1.22s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage NO_AT_BRIDGE=1 UDEV_HWDB_CHECK_CONTENTS=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=178 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py VirtualDeviceUnplugging.test_device_unplug_during_verify
----------------------------------- stdout -----------------------------------
test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:17703): libfprint-context-DEBUG: 04:24:06.525: Initializing FpContext (libfprint version 1.94.6)
(process:17703): libfprint-context-DEBUG: 04:24:06.557: No driver found for USB device 1D6B:0003
(process:17703): libfprint-context-DEBUG: 04:24:06.558: No driver found for USB device 0BDA:5401
(process:17703): libfprint-context-DEBUG: 04:24:06.559: No driver found for USB device 1D6B:0002
(process:17703): libfprint-context-DEBUG: 04:24:06.559: No driver found for USB device 1D6B:0003
(process:17703): libfprint-context-DEBUG: 04:24:06.560: No driver found for USB device 0624:0249
(process:17703): libfprint-context-DEBUG: 04:24:06.560: No driver found for USB device 0624:0248
(process:17703): libfprint-context-DEBUG: 04:24:06.561: No driver found for USB device 1D6B:0002
(process:17703): libfprint-context-DEBUG: 04:24:06.561: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-6mlep30_/virtual-device.socket
(process:17703): libfprint-context-DEBUG: 04:24:06.563: created
(process:17703): libfprint-device-DEBUG: 04:24:06.576: Device reported probe completion
(process:17703): libfprint-device-DEBUG: 04:24:06.577: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17703): libfprint-device-DEBUG: 04:24:06.578: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17703): libfprint-virtual_device-DEBUG: 04:24:06.581: 38977946179267: ../libfprint/drivers/virtual-device.c:387
(process:17703): libfprint-virtual_device_connection-DEBUG: 04:24:06.583: 38977946181116: ../libfprint/drivers/virtual-device-listener.c:153
(process:17703): libfprint-device-DEBUG: 04:24:06.586: Device reported open completion
(process:17703): libfprint-device-DEBUG: 04:24:06.587: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17703): libfprint-device-DEBUG: 04:24:06.588: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17703): libfprint-device-DEBUG: 04:24:06.597: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17703): libfprint-device-DEBUG: 04:24:06.601: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17703): libfprint-virtual_device_connection-DEBUG: 04:24:06.604: Got a new connection!
(process:17703): libfprint-virtual_device-DEBUG: 04:24:06.606: Got instructions of length 7
(process:17703): libfprint-virtual_device-DEBUG: 04:24:06.606: Received command UNPLUG
(process:17703): libfprint-device-DEBUG: 04:24:06.692: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17703): libfprint-device-DEBUG: 04:24:07.110: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY
(process:17703): libfprint-device-DEBUG: 04:24:07.110: Device reported verify completion
(process:17703): libfprint-device-DEBUG: 04:24:07.110: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17703): libfprint-device-DEBUG: 04:24:07.111: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17703): libfprint-device-DEBUG: 04:24:07.111: Updated temperature model after 0.42 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17703): libfprint-device-DEBUG: 04:24:07.116: Device reported close completion
(process:17703): libfprint-device-DEBUG: 04:24:07.117: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17703): libfprint-device-DEBUG: 04:24:07.117: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17703): libfprint-virtual_device-DEBUG: 04:24:07.127: 38977946725413: ../libfprint/drivers/virtual-device.c:752
ok
----------------------------------------------------------------------
Ran 1 test in 0.628s
OK
----------------------------------- stderr -----------------------------------
/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/../tests/virtual-device.py:426: DeprecationWarning: FPrint.Device.supports_identify is deprecated
identify=self.dev.supports_identify())
==============================================================================
=================================== 92/116 ===================================
test: libfprint:drivers / aes3500
start time: 04:24:06
duration: 2.81s
result: exit status 0
command: FP_DRIVERS_WHITELIST=aes3500 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=165 /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/aes3500
----------------------------------- stdout -----------------------------------
** (umockdev-run:17731): DEBUG: 04:24:06.975: umockdev.vala:123: Created udev test bed /tmp/umockdev.XVYLB2
** (umockdev-run:17731): DEBUG: 04:24:06.976: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1/3-1.1.3
** (umockdev-run:17731): DEBUG: 04:24:07.006: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1/3-1.1.3 (subsystem usb)
** (umockdev-run:17731): DEBUG: 04:24:07.042: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.XVYLB2/dev/bus/usb/003/004
** (umockdev-run:17731): DEBUG: 04:24:07.042: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1
** (umockdev-run:17731): DEBUG: 04:24:07.070: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1 (subsystem usb)
** (umockdev-run:17731): DEBUG: 04:24:07.129: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.XVYLB2/dev/bus/usb/003/003
** (umockdev-run:17731): DEBUG: 04:24:07.130: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1
** (umockdev-run:17731): DEBUG: 04:24:07.161: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1 (subsystem usb)
** (umockdev-run:17731): DEBUG: 04:24:07.250: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.XVYLB2/dev/bus/usb/003/002
** (umockdev-run:17731): DEBUG: 04:24:07.251: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3
** (umockdev-run:17731): DEBUG: 04:24:07.276: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3 (subsystem usb)
** (umockdev-run:17731): DEBUG: 04:24:07.312: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.XVYLB2/dev/bus/usb/003/001
** (umockdev-run:17731): DEBUG: 04:24:07.313: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0
** (umockdev-run:17731): DEBUG: 04:24:07.333: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0 (subsystem pci)
** (umockdev-run:17731): DEBUG: 04:24:07.369: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0
** (umockdev-run:17731): DEBUG: 04:24:07.382: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci)
** (umockdev-run:17731): DEBUG: 04:24:07.412: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0
** (umockdev-run:17731): DEBUG: 04:24:07.424: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci)
** (umockdev-run:17731): DEBUG: 04:24:07.456: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0
** (umockdev-run:17731): DEBUG: 04:24:07.466: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci)
(umockdev-run:17731): GLib-GIO-DEBUG: 04:24:07.498: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
(umockdev-run:17731): GLib-DEBUG: 04:24:07.522: pidfd_open(17745) failed with error: Function not implemented
(process:17745): libfprint-context-DEBUG: 04:24:07.987: Initializing FpContext (libfprint version 1.94.6)
(process:17745): libfprint-context-DEBUG: 04:24:08.051: No driver found for USB device 2230:0006
(process:17745): libfprint-context-DEBUG: 04:24:08.051: No driver found for USB device 2230:0006
(process:17745): libfprint-context-DEBUG: 04:24:08.051: No driver found for USB device 1D6B:0002
(process:17745): libfprint-device-DEBUG: 04:24:08.054: Device reported probe completion
(process:17745): libfprint-device-DEBUG: 04:24:08.054: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17745): libfprint-device-DEBUG: 04:24:08.055: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17745): libfprint-image_device-DEBUG: 04:24:08.094: Image device open completed
(process:17745): libfprint-device-DEBUG: 04:24:08.094: Device reported open completion
(process:17745): libfprint-device-DEBUG: 04:24:08.094: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17745): libfprint-device-DEBUG: 04:24:08.095: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17745): libfprint-device-DEBUG: 04:24:08.096: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17745): libfprint-image_device-DEBUG: 04:24:08.097: Activating image device
(process:17745): libfprint-image_device-DEBUG: 04:24:08.097: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17745): libfprint-aeslib-DEBUG: 04:24:08.097: write 50 regs
(process:17745): libfprint-device-DEBUG: 04:24:08.205: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17745): libfprint-aeslib-DEBUG: 04:24:08.425: all registers written
(process:17745): libfprint-image_device-DEBUG: 04:24:08.425: Image device activation completed
(process:17745): libfprint-image_device-DEBUG: 04:24:08.425: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17745): libfprint-image_device-DEBUG: 04:24:08.425: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17745): libfprint-aeslib-DEBUG: 04:24:08.426: write 6 regs
(process:17745): libfprint-device-DEBUG: 04:24:08.443: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17745): libfprint-aeslib-DEBUG: 04:24:08.514: all registers written
(process:17745): libfprint-device-DEBUG: 04:24:08.546: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17745): libfprint-image_device-DEBUG: 04:24:08.546: Image device reported finger status: on
(process:17745): libfprint-image_device-DEBUG: 04:24:08.547: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17745): libfprint-aes3k-DEBUG: 04:24:08.547: frame header byte e0
(process:17745): libfprint-aes3k-DEBUG: 04:24:08.547: frame header byte e1
(process:17745): libfprint-aes3k-DEBUG: 04:24:08.547: frame header byte e2
(process:17745): libfprint-aes3k-DEBUG: 04:24:08.547: frame header byte e3
(process:17745): libfprint-aes3k-DEBUG: 04:24:08.547: frame header byte e4
(process:17745): libfprint-aes3k-DEBUG: 04:24:08.547: frame header byte e5
(process:17745): libfprint-aes3k-DEBUG: 04:24:08.548: frame header byte e6
(process:17745): libfprint-aes3k-DEBUG: 04:24:08.548: frame header byte e7
(process:17745): libfprint-image_device-DEBUG: 04:24:08.550: Image device captured an image
(process:17745): libfprint-image_device-DEBUG: 04:24:08.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17745): libfprint-device-DEBUG: 04:24:08.551: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17745): libfprint-device-DEBUG: 04:24:08.551: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17745): libfprint-image_device-DEBUG: 04:24:08.551: Image device reported finger status: off
(process:17745): libfprint-image_device-DEBUG: 04:24:08.551: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17745): libfprint-image_device-DEBUG: 04:24:08.551: Deactivating image device
(process:17745): libfprint-image_device-DEBUG: 04:24:08.551: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17745): libfprint-image_device-DEBUG: 04:24:08.551: Image device deactivation completed
(process:17745): libfprint-image_device-DEBUG: 04:24:08.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17745): libfprint-image-DEBUG: 04:24:08.675: Minutiae scan completed in 0.120396 secs
(process:17745): libfprint-device-DEBUG: 04:24:08.678: Device reported capture completion
(process:17745): libfprint-device-DEBUG: 04:24:08.678: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17745): libfprint-device-DEBUG: 04:24:08.679: Updated temperature model after 0.47 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17745): libfprint-image_device-DEBUG: 04:24:08.685: Image device close completed
(process:17745): libfprint-device-DEBUG: 04:24:08.685: Device reported close completion
(process:17745): libfprint-device-DEBUG: 04:24:08.694: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17745): libfprint-device-DEBUG: 04:24:08.698: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17731): DEBUG: 04:24:09.238: umockdev.vala:150: Removing test bed /tmp/umockdev.XVYLB2
(umockdev-run:17731): GLib-DEBUG: 04:24:09.356: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-pbet284d/capture.png and /<<PKGBUILDDIR>>/tests/aes3500/capture.png
==============================================================================
=================================== 93/116 ===================================
test: libfprint:drivers / elan
start time: 04:24:06
duration: 5.59s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints FP_DRIVERS_WHITELIST=elan G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=115 /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/elan
----------------------------------- stdout -----------------------------------
** (umockdev-run:17730): DEBUG: 04:24:06.970: umockdev.vala:123: Created udev test bed /tmp/umockdev.NALLB2
** (umockdev-run:17730): DEBUG: 04:24:06.971: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4
** (umockdev-run:17730): DEBUG: 04:24:06.994: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 (subsystem usb)
** (umockdev-run:17730): DEBUG: 04:24:07.061: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.NALLB2/dev/bus/usb/001/094
** (umockdev-run:17730): DEBUG: 04:24:07.063: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4
** (umockdev-run:17730): DEBUG: 04:24:07.082: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb)
** (umockdev-run:17730): DEBUG: 04:24:07.138: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.NALLB2/dev/bus/usb/001/083
** (umockdev-run:17730): DEBUG: 04:24:07.139: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17730): DEBUG: 04:24:07.154: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17730): DEBUG: 04:24:07.199: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.NALLB2/dev/bus/usb/001/001
** (umockdev-run:17730): DEBUG: 04:24:07.200: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17730): DEBUG: 04:24:07.205: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17730): GLib-GIO-DEBUG: 04:24:07.262: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
(umockdev-run:17730): GLib-DEBUG: 04:24:07.327: pidfd_open(17741) failed with error: Function not implemented
(process:17741): libfprint-context-DEBUG: 04:24:07.780: Initializing FpContext (libfprint version 1.94.6)
(process:17741): libfprint-context-DEBUG: 04:24:07.824: No driver found for USB device 17EF:1018
(process:17741): libfprint-context-DEBUG: 04:24:07.825: No driver found for USB device 1D6B:0002
(process:17741): libfprint-device-DEBUG: 04:24:07.828: Device reported probe completion
(process:17741): libfprint-device-DEBUG: 04:24:07.829: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17741): libfprint-device-DEBUG: 04:24:07.829: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17741): libfprint-elan-DEBUG: 04:24:07.885: 38977947482778: ../libfprint/drivers/elan.c:908
(process:17741): libfprint-image_device-DEBUG: 04:24:07.893: Image device open completed
(process:17741): libfprint-device-DEBUG: 04:24:07.894: Device reported open completion
(process:17741): libfprint-device-DEBUG: 04:24:07.894: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17741): libfprint-device-DEBUG: 04:24:07.894: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17741): libfprint-device-DEBUG: 04:24:07.896: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17741): libfprint-image_device-DEBUG: 04:24:07.896: Activating image device
(process:17741): libfprint-image_device-DEBUG: 04:24:07.896: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17741): libfprint-elan-DEBUG: 04:24:07.896: 38977947494684: ../libfprint/drivers/elan.c:960
(process:17741): libfprint-elan-DEBUG: 04:24:07.897: 38977947494786: ../libfprint/drivers/elan.c:951
(process:17741): libfprint-elan-DEBUG: 04:24:07.897: 38977947494861: ../libfprint/drivers/elan.c:892
(process:17741): libfprint-elan-DEBUG: 04:24:07.897: 38977947494933: ../libfprint/drivers/elan.c:100
(process:17741): libfprint-SSM-DEBUG: 04:24:07.897: [elan] ACTIVATE_NUM_STATES entering state 0
(process:17741): libfprint-elan-DEBUG: 04:24:07.897: 38977947495126: ../libfprint/drivers/elan.c:820
(process:17741): libfprint-elan-DEBUG: 04:24:07.918: 38977947516294: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:07.918: 38977947516451: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:07.918: 38977947516539: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:07.955: 38977947553095: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:07.955: 38977947553265: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:07.955: [elan] ACTIVATE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:07.955: 38977947553447: ../libfprint/drivers/elan.c:820
(process:17741): libfprint-elan-DEBUG: 04:24:07.955: FW ver 0x0140
(process:17741): libfprint-SSM-DEBUG: 04:24:07.955: [elan] ACTIVATE_NUM_STATES entering state 2
(process:17741): libfprint-elan-DEBUG: 04:24:07.955: 38977947553697: ../libfprint/drivers/elan.c:820
(process:17741): libfprint-elan-DEBUG: 04:24:07.986: 38977947584124: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:07.986: 38977947584289: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:07.986: 38977947584375: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-device-DEBUG: 04:24:08.003: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17741): libfprint-elan-DEBUG: 04:24:08.017: 38977947614863: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.017: 38977947615018: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.017: [elan] ACTIVATE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:08.017: 38977947615184: ../libfprint/drivers/elan.c:820
(process:17741): libfprint-elan-DEBUG: 04:24:08.017: sensor dimensions, WxH: 144x64
(process:17741): libfprint-SSM-DEBUG: 04:24:08.017: [elan] ACTIVATE_NUM_STATES entering state 4
(process:17741): libfprint-elan-DEBUG: 04:24:08.017: 38977947615432: ../libfprint/drivers/elan.c:820
(process:17741): libfprint-elan-DEBUG: 04:24:08.017: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0)
(process:17741): libfprint-elan-DEBUG: 04:24:08.017: 38977947615610: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.017: [elan] ACTIVATE_NUM_STATES completed successfully
(process:17741): libfprint-elan-DEBUG: 04:24:08.018: 38977947615786: ../libfprint/drivers/elan.c:881
(process:17741): libfprint-image_device-DEBUG: 04:24:08.018: Image device activation completed
(process:17741): libfprint-image_device-DEBUG: 04:24:08.018: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17741): libfprint-elan-DEBUG: 04:24:08.018: 38977947616177: ../libfprint/drivers/elan.c:960
(process:17741): libfprint-image_device-DEBUG: 04:24:08.018: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17741): libfprint-elan-DEBUG: 04:24:08.018: 38977947616425: ../libfprint/drivers/elan.c:960
(process:17741): libfprint-elan-DEBUG: 04:24:08.018: 38977947616509: ../libfprint/drivers/elan.c:792
(process:17741): libfprint-elan-DEBUG: 04:24:08.018: 38977947616575: ../libfprint/drivers/elan.c:100
(process:17741): libfprint-SSM-DEBUG: 04:24:08.018: [elan] CALIBRATE_NUM_STATES entering state 0
(process:17741): libfprint-elan-DEBUG: 04:24:08.018: 38977947616746: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-device-DEBUG: 04:24:08.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17741): libfprint-elan-DEBUG: 04:24:08.054: 38977947652039: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.054: 38977947652162: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.054: 38977947652239: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.087: 38977947684894: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.087: 38977947685055: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.087: [elan] CALIBRATE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:08.087: 38977947685194: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.087: 38977947685252: ../libfprint/drivers/elan.c:156
(process:17741): libfprint-elan-DEBUG: 04:24:08.087: 38977947685338: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:08.087: [elan] CALIBRATE_NUM_STATES entering state 2
(process:17741): libfprint-elan-DEBUG: 04:24:08.087: 38977947685495: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.129: 38977947726943: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.129: 38977947727131: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.129: 38977947727228: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.162: 38977947760093: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.162: 38977947760246: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.162: [elan] CALIBRATE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:08.162: 38977947760420: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.162: 38977947760504: ../libfprint/drivers/elan.c:634
(process:17741): libfprint-elan-DEBUG: 04:24:08.162: calibration mean: 8421, bg mean: 5805, delta: 2616
(process:17741): libfprint-SSM-DEBUG: 04:24:08.162: [elan] CALIBRATE_NUM_STATES entering state 4
(process:17741): libfprint-elan-DEBUG: 04:24:08.163: 38977947760804: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.197: 38977947795351: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.197: 38977947795488: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.197: 38977947795562: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.226: 38977947824444: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.226: 38977947824603: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.226: [elan] CALIBRATE_NUM_STATES entering state 5
(process:17741): libfprint-elan-DEBUG: 04:24:08.227: 38977947824779: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.227: calibration status: 0x01
(process:17741): libfprint-SSM-DEBUG: 04:24:08.277: [elan] CALIBRATE_NUM_STATES entering state 6
(process:17741): libfprint-elan-DEBUG: 04:24:08.277: 38977947875649: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-SSM-DEBUG: 04:24:08.277: [elan] CALIBRATE_NUM_STATES entering state 4
(process:17741): libfprint-elan-DEBUG: 04:24:08.278: 38977947875836: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.311: 38977947908797: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.311: 38977947908966: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.311: 38977947909060: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.340: 38977947938344: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.340: 38977947938502: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.340: [elan] CALIBRATE_NUM_STATES entering state 5
(process:17741): libfprint-elan-DEBUG: 04:24:08.340: 38977947938694: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.341: calibration status: 0x01
(process:17741): libfprint-SSM-DEBUG: 04:24:08.390: [elan] CALIBRATE_NUM_STATES entering state 6
(process:17741): libfprint-elan-DEBUG: 04:24:08.390: 38977947988602: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-SSM-DEBUG: 04:24:08.390: [elan] CALIBRATE_NUM_STATES entering state 4
(process:17741): libfprint-elan-DEBUG: 04:24:08.391: 38977947988799: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.416: 38977948014308: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.416: 38977948014427: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.416: 38977948014520: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.450: 38977948048160: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.450: 38977948048311: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.450: [elan] CALIBRATE_NUM_STATES entering state 5
(process:17741): libfprint-elan-DEBUG: 04:24:08.450: 38977948048510: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.450: calibration status: 0x01
(process:17741): libfprint-SSM-DEBUG: 04:24:08.501: [elan] CALIBRATE_NUM_STATES entering state 6
(process:17741): libfprint-elan-DEBUG: 04:24:08.501: 38977948099427: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-SSM-DEBUG: 04:24:08.501: [elan] CALIBRATE_NUM_STATES entering state 4
(process:17741): libfprint-elan-DEBUG: 04:24:08.501: 38977948099625: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.531: 38977948129337: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.531: 38977948129472: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.531: 38977948129566: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.568: 38977948166688: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.569: 38977948166829: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.569: [elan] CALIBRATE_NUM_STATES entering state 5
(process:17741): libfprint-elan-DEBUG: 04:24:08.569: 38977948167024: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.569: calibration status: 0x01
(process:17741): libfprint-SSM-DEBUG: 04:24:08.620: [elan] CALIBRATE_NUM_STATES entering state 6
(process:17741): libfprint-elan-DEBUG: 04:24:08.620: 38977948217881: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-SSM-DEBUG: 04:24:08.620: [elan] CALIBRATE_NUM_STATES entering state 4
(process:17741): libfprint-elan-DEBUG: 04:24:08.620: 38977948218019: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.644: 38977948242329: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.644: 38977948242490: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.644: 38977948242562: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.677: 38977948275231: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.677: 38977948275367: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.677: [elan] CALIBRATE_NUM_STATES entering state 5
(process:17741): libfprint-elan-DEBUG: 04:24:08.677: 38977948275562: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.677: calibration status: 0x01
(process:17741): libfprint-SSM-DEBUG: 04:24:08.728: [elan] CALIBRATE_NUM_STATES entering state 6
(process:17741): libfprint-elan-DEBUG: 04:24:08.728: 38977948326467: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-SSM-DEBUG: 04:24:08.728: [elan] CALIBRATE_NUM_STATES entering state 4
(process:17741): libfprint-elan-DEBUG: 04:24:08.728: 38977948326665: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.758: 38977948356097: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.758: 38977948356245: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.758: 38977948356325: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.791: 38977948389134: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.791: 38977948389306: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.791: [elan] CALIBRATE_NUM_STATES entering state 5
(process:17741): libfprint-elan-DEBUG: 04:24:08.791: 38977948389495: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.791: calibration status: 0x03
(process:17741): libfprint-SSM-DEBUG: 04:24:08.791: [elan] CALIBRATE_NUM_STATES entering state 0
(process:17741): libfprint-elan-DEBUG: 04:24:08.791: 38977948389756: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.818: 38977948416635: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.819: 38977948416799: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.819: 38977948416890: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.847: 38977948445332: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.847: 38977948445517: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.847: [elan] CALIBRATE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:08.847: 38977948445705: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.848: 38977948445785: ../libfprint/drivers/elan.c:156
(process:17741): libfprint-elan-DEBUG: 04:24:08.848: 38977948445873: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:08.848: [elan] CALIBRATE_NUM_STATES entering state 2
(process:17741): libfprint-elan-DEBUG: 04:24:08.848: 38977948446071: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.878: 38977948476727: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.879: 38977948476874: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.879: 38977948476963: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.907: 38977948505187: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.907: 38977948505347: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.907: [elan] CALIBRATE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:08.907: 38977948505528: ../libfprint/drivers/elan.c:691
(process:17741): libfprint-elan-DEBUG: 04:24:08.907: 38977948505603: ../libfprint/drivers/elan.c:634
(process:17741): libfprint-elan-DEBUG: 04:24:08.907: calibration mean: 8339, bg mean: 8146, delta: 193
(process:17741): libfprint-SSM-DEBUG: 04:24:08.908: [elan] CALIBRATE_NUM_STATES completed successfully
(process:17741): libfprint-elan-DEBUG: 04:24:08.908: 38977948505881: ../libfprint/drivers/elan.c:776
(process:17741): libfprint-elan-DEBUG: 04:24:08.908: 38977948505966: ../libfprint/drivers/elan.c:620
(process:17741): libfprint-elan-DEBUG: 04:24:08.908: 38977948506043: ../libfprint/drivers/elan.c:100
(process:17741): libfprint-SSM-DEBUG: 04:24:08.908: [elan] CAPTURE_NUM_STATES entering state 0
(process:17741): libfprint-elan-DEBUG: 04:24:08.938: 38977948536720: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.939: 38977948536848: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.939: 38977948536933: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.939: skipping read, not expecting anything
(process:17741): libfprint-elan-DEBUG: 04:24:08.939: 38977948537095: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.939: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:08.970: 38977948568500: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.970: 38977948568637: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:08.970: 38977948568708: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:08.999: 38977948597396: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:08.999: 38977948597507: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:08.999: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-device-DEBUG: 04:24:08.999: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17741): libfprint-image_device-DEBUG: 04:24:09.000: Image device reported finger status: on
(process:17741): libfprint-image_device-DEBUG: 04:24:09.000: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17741): libfprint-elan-DEBUG: 04:24:09.000: 38977948598102: ../libfprint/drivers/elan.c:960
(process:17741): libfprint-elan-DEBUG: 04:24:09.027: 38977948625197: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.027: 38977948625339: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.027: 38977948625417: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.060: 38977948658515: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.060: 38977948658698: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.061: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:09.061: 38977948658882: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:09.061: 38977948658987: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:09.061: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:09.087: 38977948685708: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.088: 38977948685845: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.088: 38977948685923: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.121: 38977948719255: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.121: 38977948719407: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.121: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:09.121: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:09.148: 38977948746412: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.148: 38977948746557: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.148: 38977948746650: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.178: 38977948775899: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.186: 38977948784138: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.186: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:09.186: 38977948784360: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:09.186: 38977948784456: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:09.186: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:09.213: 38977948811427: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.213: 38977948811593: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.213: 38977948811681: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.241: 38977948839130: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.241: 38977948839270: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.241: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:09.241: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:09.270: 38977948868017: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.270: 38977948868165: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.270: 38977948868250: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.304: 38977948901947: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.304: 38977948902129: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.304: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:09.304: 38977948902325: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:09.304: 38977948902431: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:09.304: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:09.338: 38977948935923: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.338: 38977948936072: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.338: 38977948936158: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.367: 38977948965729: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.368: 38977948965854: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.368: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:09.368: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:09.398: 38977948996211: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.398: 38977948996344: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.398: 38977948996434: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.438: 38977949036118: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.438: 38977949036270: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.438: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:09.438: 38977949036453: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:09.438: 38977949036559: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:09.438: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:09.477: 38977949075185: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.477: 38977949075305: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.477: 38977949075368: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.558: 38977949156121: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.558: 38977949156268: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.558: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:09.558: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:09.611: 38977949209552: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.611: 38977949209694: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.612: 38977949209771: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.632: 38977949230486: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.632: 38977949230644: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.632: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:09.633: 38977949230812: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:09.633: 38977949230908: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:09.633: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:09.651: 38977949249240: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.651: 38977949249370: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.651: 38977949249448: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.672: 38977949270057: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.672: 38977949270189: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.672: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:09.672: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:09.691: 38977949289261: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.691: 38977949289390: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.691: 38977949289471: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.713: 38977949311292: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.713: 38977949311456: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.713: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:09.713: 38977949311629: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:09.713: 38977949311719: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:09.714: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:09.733: 38977949330887: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.733: 38977949331022: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.733: 38977949331102: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.754: 38977949352488: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.754: 38977949352635: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.754: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:09.755: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:09.773: 38977949371536: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.773: 38977949371693: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.774: 38977949371779: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.796: 38977949394555: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.796: 38977949394680: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.797: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:09.797: 38977949394842: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:09.797: 38977949394930: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:09.797: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:09.816: 38977949413948: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.816: 38977949414078: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.816: 38977949414161: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.839: 38977949437259: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.839: 38977949437391: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.839: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:09.839: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:09.859: 38977949456794: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.859: 38977949456935: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.859: 38977949457014: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.880: 38977949477922: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.880: 38977949478071: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.880: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:09.880: 38977949478237: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:09.880: 38977949478327: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:09.880: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:09.900: 38977949498202: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.900: 38977949498370: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.900: 38977949498445: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.924: 38977949522524: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.924: 38977949522669: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.924: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:09.925: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:09.944: 38977949541755: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.944: 38977949541895: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.944: 38977949541967: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:09.967: 38977949564896: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.967: 38977949565054: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:09.967: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:09.967: 38977949565235: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:09.967: 38977949565327: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:09.967: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:09.986: 38977949584327: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:09.986: 38977949584464: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:09.986: 38977949584544: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:10.008: 38977949606087: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.008: 38977949606235: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:10.008: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:10.008: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:10.044: 38977949641772: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.044: 38977949641922: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:10.044: 38977949642002: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:10.089: 38977949687181: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.089: 38977949687348: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:10.089: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:10.089: 38977949687500: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:10.089: 38977949687578: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:10.089: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:10.111: 38977949708960: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.111: 38977949709113: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:10.111: 38977949709197: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:10.132: 38977949729750: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.132: 38977949729892: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:10.132: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:10.132: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:10.151: 38977949748780: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.151: 38977949748919: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:10.151: 38977949748991: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:10.172: 38977949769804: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.172: 38977949769976: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:10.172: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:10.172: 38977949770144: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:10.172: 38977949770243: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:10.172: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:10.198: 38977949796582: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.198: 38977949796700: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:10.198: 38977949796764: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:10.227: 38977949825333: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.227: 38977949825491: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:10.227: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-image_device-DEBUG: 04:24:10.227: Image device reported finger status: on
(process:17741): libfprint-elan-DEBUG: 04:24:10.261: 38977949858996: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.261: 38977949859138: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:10.261: 38977949859208: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:10.293: 38977949891240: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.293: 38977949891411: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:10.293: [elan] CAPTURE_NUM_STATES entering state 3
(process:17741): libfprint-elan-DEBUG: 04:24:10.293: 38977949891555: ../libfprint/drivers/elan.c:203
(process:17741): libfprint-elan-DEBUG: 04:24:10.293: 38977949891637: ../libfprint/drivers/elan.c:118
(process:17741): libfprint-SSM-DEBUG: 04:24:10.294: [elan] CAPTURE_NUM_STATES entering state 1
(process:17741): libfprint-elan-DEBUG: 04:24:10.328: 38977949926428: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.328: 38977949926550: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:10.328: 38977949926627: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:10.359: 38977949957370: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:10.359: 38977949957551: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:10.359: [elan] CAPTURE_NUM_STATES entering state 2
(process:17741): libfprint-SSM-DEBUG: 04:24:10.359: [elan] CAPTURE_NUM_STATES completed successfully
(process:17741): libfprint-elan-DEBUG: 04:24:10.360: 38977949957824: ../libfprint/drivers/elan.c:586
(process:17741): libfprint-elan-DEBUG: 04:24:10.360: 38977949957897: ../libfprint/drivers/elan.c:315
(process:17741): libfprint-elan-DEBUG: 04:24:10.360: 38977949957981: ../libfprint/drivers/elan.c:272
(process:17741): libfprint-elan-DEBUG: 04:24:10.361: 38977949959541: ../libfprint/drivers/elan.c:272
(process:17741): libfprint-elan-DEBUG: 04:24:10.363: 38977949961178: ../libfprint/drivers/elan.c:272
(process:17741): libfprint-elan-DEBUG: 04:24:10.365: 38977949962758: ../libfprint/drivers/elan.c:272
(process:17741): libfprint-elan-DEBUG: 04:24:10.366: 38977949964378: ../libfprint/drivers/elan.c:272
(process:17741): libfprint-elan-DEBUG: 04:24:10.368: 38977949965962: ../libfprint/drivers/elan.c:272
(process:17741): libfprint-elan-DEBUG: 04:24:10.369: 38977949967565: ../libfprint/drivers/elan.c:272
(process:17741): libfprint-elan-DEBUG: 04:24:10.375: 38977949973220: ../libfprint/drivers/elan.c:272
(process:17741): libfprint-elan-DEBUG: 04:24:10.377: 38977949974851: ../libfprint/drivers/elan.c:272
(process:17741): libfprint-elan-DEBUG: 04:24:10.378: 38977949976472: ../libfprint/drivers/elan.c:272
(process:17741): libfprint-assembling-DEBUG: 04:24:10.979: calc delta completed in 0.598726 secs
(process:17741): libfprint-assembling-DEBUG: 04:24:11.529: calc delta completed in 0.549751 secs
(process:17741): libfprint-assembling-DEBUG: 04:24:11.529: errors: 233151 rev: 207411
(process:17741): libfprint-assembling-DEBUG: 04:24:11.529: height is -185
(process:17741): libfprint-image_device-DEBUG: 04:24:11.538: Image device captured an image
(process:17741): libfprint-image_device-DEBUG: 04:24:11.538: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17741): libfprint-elan-DEBUG: 04:24:11.539: 38977951136774: ../libfprint/drivers/elan.c:960
(process:17741): libfprint-device-DEBUG: 04:24:11.539: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17741): libfprint-elan-DEBUG: 04:24:11.539: 38977951137055: ../libfprint/drivers/elan.c:507
(process:17741): libfprint-elan-DEBUG: 04:24:11.539: 38977951137145: ../libfprint/drivers/elan.c:100
(process:17741): libfprint-SSM-DEBUG: 04:24:11.539: [elan] STOP_CAPTURE_NUM_STATES entering state 0
(process:17741): libfprint-elan-DEBUG: 04:24:11.539: 38977951137401: ../libfprint/drivers/elan.c:466
(process:17741): libfprint-elan-DEBUG: 04:24:11.587: 38977951185732: ../libfprint/drivers/elan.c:346
(process:17741): libfprint-elan-DEBUG: 04:24:11.588: 38977951185840: ../libfprint/drivers/elan.c:366
(process:17741): libfprint-elan-DEBUG: 04:24:11.588: 38977951185901: ../libfprint/drivers/elan.c:379
(process:17741): libfprint-elan-DEBUG: 04:24:11.588: skipping read, not expecting anything
(process:17741): libfprint-elan-DEBUG: 04:24:11.588: 38977951186019: ../libfprint/drivers/elan.c:335
(process:17741): libfprint-SSM-DEBUG: 04:24:11.588: [elan] STOP_CAPTURE_NUM_STATES completed successfully
(process:17741): libfprint-elan-DEBUG: 04:24:11.588: 38977951186149: ../libfprint/drivers/elan.c:483
(process:17741): libfprint-device-DEBUG: 04:24:11.588: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17741): libfprint-image_device-DEBUG: 04:24:11.588: Image device reported finger status: off
(process:17741): libfprint-image_device-DEBUG: 04:24:11.588: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17741): libfprint-elan-DEBUG: 04:24:11.588: 38977951186555: ../libfprint/drivers/elan.c:960
(process:17741): libfprint-image_device-DEBUG: 04:24:11.588: Deactivating image device
(process:17741): libfprint-image_device-DEBUG: 04:24:11.588: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17741): libfprint-elan-DEBUG: 04:24:11.589: 38977951186826: ../libfprint/drivers/elan.c:960
(process:17741): libfprint-elan-DEBUG: 04:24:11.589: 38977951186895: ../libfprint/drivers/elan.c:975
(process:17741): libfprint-image_device-DEBUG: 04:24:11.589: Image device deactivation completed
(process:17741): libfprint-image_device-DEBUG: 04:24:11.589: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17741): libfprint-elan-DEBUG: 04:24:11.589: 38977951187151: ../libfprint/drivers/elan.c:960
(process:17741): libfprint-image-DEBUG: 04:24:11.609: Minutiae scan completed in 0.066951 secs
(process:17741): libfprint-device-DEBUG: 04:24:11.614: Device reported capture completion
(process:17741): libfprint-device-DEBUG: 04:24:11.615: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17741): libfprint-device-DEBUG: 04:24:11.615: Updated temperature model after 3.61 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17741): libfprint-elan-DEBUG: 04:24:11.616: 38977951214129: ../libfprint/drivers/elan.c:939
(process:17741): libfprint-elan-DEBUG: 04:24:11.616: 38977951214237: ../libfprint/drivers/elan.c:100
(process:17741): libfprint-image_device-DEBUG: 04:24:11.623: Image device close completed
(process:17741): libfprint-device-DEBUG: 04:24:11.623: Device reported close completion
(process:17741): libfprint-device-DEBUG: 04:24:11.632: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17741): libfprint-device-DEBUG: 04:24:11.632: Updated temperature model after 0.02 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17730): DEBUG: 04:24:12.126: umockdev.vala:150: Removing test bed /tmp/umockdev.NALLB2
(umockdev-run:17730): GLib-DEBUG: 04:24:12.178: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-9muf_nsb/capture.png and /<<PKGBUILDDIR>>/tests/elan/capture.png
----------------------------------- stderr -----------------------------------
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
==============================================================================
=================================== 94/116 ===================================
test: libfprint:drivers / elan-cobo
start time: 04:24:07
duration: 5.50s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints FP_DRIVERS_WHITELIST=elan G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=239 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/elan-cobo
----------------------------------- stdout -----------------------------------
** (umockdev-run:17743): DEBUG: 04:24:07.518: umockdev.vala:123: Created udev test bed /tmp/umockdev.CXC9A2
** (umockdev-run:17743): DEBUG: 04:24:07.519: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10
** (umockdev-run:17743): DEBUG: 04:24:07.533: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb)
** (umockdev-run:17743): DEBUG: 04:24:07.563: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.CXC9A2/dev/bus/usb/001/045
** (umockdev-run:17743): DEBUG: 04:24:07.564: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17743): DEBUG: 04:24:07.585: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17743): DEBUG: 04:24:07.623: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.CXC9A2/dev/bus/usb/001/001
** (umockdev-run:17743): DEBUG: 04:24:07.623: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17743): DEBUG: 04:24:07.632: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17743): GLib-DEBUG: 04:24:07.674: pidfd_open(17747) failed with error: Function not implemented
(process:17747): libfprint-context-DEBUG: 04:24:08.153: Initializing FpContext (libfprint version 1.94.6)
(process:17747): libfprint-context-DEBUG: 04:24:08.190: No driver found for USB device 1D6B:0002
(process:17747): libfprint-device-DEBUG: 04:24:08.193: Device reported probe completion
(process:17747): libfprint-device-DEBUG: 04:24:08.193: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17747): libfprint-device-DEBUG: 04:24:08.199: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17747): libfprint-elan-DEBUG: 04:24:08.234: 38977947832172: ../libfprint/drivers/elan.c:908
(process:17747): libfprint-image_device-DEBUG: 04:24:08.241: Image device open completed
(process:17747): libfprint-device-DEBUG: 04:24:08.241: Device reported open completion
(process:17747): libfprint-device-DEBUG: 04:24:08.241: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17747): libfprint-device-DEBUG: 04:24:08.241: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17747): libfprint-device-DEBUG: 04:24:08.243: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17747): libfprint-image_device-DEBUG: 04:24:08.243: Activating image device
(process:17747): libfprint-image_device-DEBUG: 04:24:08.244: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17747): libfprint-elan-DEBUG: 04:24:08.244: 38977947842025: ../libfprint/drivers/elan.c:960
(process:17747): libfprint-elan-DEBUG: 04:24:08.244: 38977947842131: ../libfprint/drivers/elan.c:951
(process:17747): libfprint-elan-DEBUG: 04:24:08.244: 38977947842218: ../libfprint/drivers/elan.c:892
(process:17747): libfprint-elan-DEBUG: 04:24:08.244: 38977947842295: ../libfprint/drivers/elan.c:100
(process:17747): libfprint-SSM-DEBUG: 04:24:08.244: [elan] ACTIVATE_NUM_STATES entering state 0
(process:17747): libfprint-elan-DEBUG: 04:24:08.244: 38977947842496: ../libfprint/drivers/elan.c:820
(process:17747): libfprint-elan-DEBUG: 04:24:08.275: 38977947873117: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.275: 38977947873277: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.275: 38977947873368: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.313: 38977947911569: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.313: 38977947911716: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.314: [elan] ACTIVATE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:08.314: 38977947911896: ../libfprint/drivers/elan.c:820
(process:17747): libfprint-elan-DEBUG: 04:24:08.314: FW ver 0x0140
(process:17747): libfprint-SSM-DEBUG: 04:24:08.314: [elan] ACTIVATE_NUM_STATES entering state 2
(process:17747): libfprint-elan-DEBUG: 04:24:08.314: 38977947912180: ../libfprint/drivers/elan.c:820
(process:17747): libfprint-elan-DEBUG: 04:24:08.345: 38977947942966: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.345: 38977947943102: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.345: 38977947943192: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-device-DEBUG: 04:24:08.363: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17747): libfprint-elan-DEBUG: 04:24:08.379: 38977947976777: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.379: 38977947976944: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.379: [elan] ACTIVATE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:08.379: 38977947977129: ../libfprint/drivers/elan.c:820
(process:17747): libfprint-elan-DEBUG: 04:24:08.379: sensor dimensions, WxH: 144x64
(process:17747): libfprint-SSM-DEBUG: 04:24:08.379: [elan] ACTIVATE_NUM_STATES entering state 4
(process:17747): libfprint-elan-DEBUG: 04:24:08.379: 38977947977410: ../libfprint/drivers/elan.c:820
(process:17747): libfprint-elan-DEBUG: 04:24:08.379: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0)
(process:17747): libfprint-elan-DEBUG: 04:24:08.379: 38977947977599: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.379: [elan] ACTIVATE_NUM_STATES completed successfully
(process:17747): libfprint-elan-DEBUG: 04:24:08.380: 38977947977773: ../libfprint/drivers/elan.c:881
(process:17747): libfprint-image_device-DEBUG: 04:24:08.380: Image device activation completed
(process:17747): libfprint-image_device-DEBUG: 04:24:08.380: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17747): libfprint-elan-DEBUG: 04:24:08.380: 38977947978154: ../libfprint/drivers/elan.c:960
(process:17747): libfprint-image_device-DEBUG: 04:24:08.380: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17747): libfprint-elan-DEBUG: 04:24:08.380: 38977947978451: ../libfprint/drivers/elan.c:960
(process:17747): libfprint-elan-DEBUG: 04:24:08.380: 38977947978535: ../libfprint/drivers/elan.c:792
(process:17747): libfprint-elan-DEBUG: 04:24:08.380: 38977947978613: ../libfprint/drivers/elan.c:100
(process:17747): libfprint-SSM-DEBUG: 04:24:08.380: [elan] CALIBRATE_NUM_STATES entering state 0
(process:17747): libfprint-elan-DEBUG: 04:24:08.381: 38977947978801: ../libfprint/drivers/elan.c:691
(process:17747): libfprint-device-DEBUG: 04:24:08.398: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17747): libfprint-elan-DEBUG: 04:24:08.416: 38977948013897: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.416: 38977948014042: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.416: 38977948014126: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.451: 38977948048771: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.451: 38977948048916: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.451: [elan] CALIBRATE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:08.451: 38977948049100: ../libfprint/drivers/elan.c:691
(process:17747): libfprint-elan-DEBUG: 04:24:08.451: 38977948049182: ../libfprint/drivers/elan.c:156
(process:17747): libfprint-elan-DEBUG: 04:24:08.451: 38977948049302: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:08.451: [elan] CALIBRATE_NUM_STATES entering state 2
(process:17747): libfprint-elan-DEBUG: 04:24:08.451: 38977948049529: ../libfprint/drivers/elan.c:691
(process:17747): libfprint-elan-DEBUG: 04:24:08.486: 38977948084595: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.487: 38977948084761: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.487: 38977948084845: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.520: 38977948118165: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.520: 38977948118313: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.520: [elan] CALIBRATE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:08.520: 38977948118496: ../libfprint/drivers/elan.c:691
(process:17747): libfprint-elan-DEBUG: 04:24:08.520: 38977948118579: ../libfprint/drivers/elan.c:634
(process:17747): libfprint-elan-DEBUG: 04:24:08.520: calibration mean: 8248, bg mean: 7978, delta: 270
(process:17747): libfprint-SSM-DEBUG: 04:24:08.521: [elan] CALIBRATE_NUM_STATES completed successfully
(process:17747): libfprint-elan-DEBUG: 04:24:08.521: 38977948118865: ../libfprint/drivers/elan.c:776
(process:17747): libfprint-elan-DEBUG: 04:24:08.521: 38977948118944: ../libfprint/drivers/elan.c:620
(process:17747): libfprint-elan-DEBUG: 04:24:08.521: 38977948119017: ../libfprint/drivers/elan.c:100
(process:17747): libfprint-SSM-DEBUG: 04:24:08.521: [elan] CAPTURE_NUM_STATES entering state 0
(process:17747): libfprint-elan-DEBUG: 04:24:08.552: 38977948150199: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.552: 38977948150314: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.552: 38977948150401: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.552: skipping read, not expecting anything
(process:17747): libfprint-elan-DEBUG: 04:24:08.552: 38977948150553: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.552: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:08.583: 38977948181567: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.583: 38977948181712: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.584: 38977948181790: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.617: 38977948214820: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.617: 38977948214972: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.617: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-device-DEBUG: 04:24:08.617: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17747): libfprint-image_device-DEBUG: 04:24:08.617: Image device reported finger status: on
(process:17747): libfprint-image_device-DEBUG: 04:24:08.617: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17747): libfprint-elan-DEBUG: 04:24:08.617: 38977948215552: ../libfprint/drivers/elan.c:960
(process:17747): libfprint-elan-DEBUG: 04:24:08.648: 38977948246593: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.648: 38977948246724: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.649: 38977948246804: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.678: 38977948275903: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.685: 38977948283216: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.685: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:08.685: 38977948283407: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:08.685: 38977948283514: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:08.685: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:08.718: 38977948316120: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.718: 38977948316279: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.718: 38977948316356: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.749: 38977948347324: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.749: 38977948347502: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.749: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:08.749: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:08.776: 38977948373996: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.776: 38977948374146: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.776: 38977948374230: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.809: 38977948406863: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.809: 38977948407064: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.809: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:08.809: 38977948407279: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:08.809: 38977948407389: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:08.809: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:08.837: 38977948435448: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.837: 38977948435613: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.837: 38977948435698: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.873: 38977948470836: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.873: 38977948470998: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.873: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:08.873: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:08.901: 38977948498947: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.901: 38977948499102: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.901: 38977948499183: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.936: 38977948534238: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.936: 38977948534415: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.936: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:08.936: 38977948534595: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:08.936: 38977948534688: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:08.937: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:08.957: 38977948555080: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.957: 38977948555237: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.957: 38977948555327: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:08.979: 38977948577168: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.979: 38977948577311: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:08.979: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:08.979: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:08.998: 38977948596606: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:08.998: 38977948596754: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:08.999: 38977948596837: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.022: 38977948619974: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.022: 38977948620170: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.022: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.022: 38977948620363: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.022: 38977948620463: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.022: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.043: 38977948641497: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.043: 38977948641639: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.043: 38977948641715: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.067: 38977948664744: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.067: 38977948664882: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.067: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:09.067: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:09.086: 38977948684086: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.086: 38977948684240: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.086: 38977948684318: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.109: 38977948706753: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.109: 38977948706924: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.109: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.109: 38977948707100: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.109: 38977948707200: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.109: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.129: 38977948726814: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.129: 38977948726949: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.129: 38977948727035: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.151: 38977948749003: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.151: 38977948749138: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.151: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:09.151: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:09.170: 38977948768320: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.170: 38977948768467: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.170: 38977948768548: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.193: 38977948791108: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.193: 38977948791281: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.193: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.193: 38977948791470: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.193: 38977948791579: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.193: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.214: 38977948811762: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.214: 38977948811873: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.214: 38977948811950: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.235: 38977948832782: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.235: 38977948832942: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.235: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:09.235: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:09.253: 38977948851316: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.253: 38977948851469: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.253: 38977948851550: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.275: 38977948872953: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.275: 38977948873115: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.275: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.275: 38977948873301: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.275: 38977948873401: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.275: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.294: 38977948892072: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.294: 38977948892235: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.294: 38977948892333: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.315: 38977948913431: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.315: 38977948913583: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.315: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:09.316: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:09.335: 38977948933014: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.335: 38977948933136: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.335: 38977948933220: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.356: 38977948954286: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.356: 38977948954419: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.356: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.356: 38977948954604: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.356: 38977948954702: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.357: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.375: 38977948973661: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.376: 38977948973791: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.376: 38977948973879: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.396: 38977948994116: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.396: 38977948994283: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.396: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:09.396: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:09.415: 38977949013152: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.415: 38977949013312: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.415: 38977949013406: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.437: 38977949035000: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.437: 38977949035186: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.437: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.437: 38977949035380: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.437: 38977949035492: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.437: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.459: 38977949057272: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.459: 38977949057434: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.459: 38977949057524: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.480: 38977949078164: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.480: 38977949078291: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.480: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:09.480: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:09.499: 38977949097056: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.499: 38977949097212: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.499: 38977949097286: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.520: 38977949117963: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.520: 38977949118149: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.520: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.520: 38977949118329: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.520: 38977949118426: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.520: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.539: 38977949136775: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.539: 38977949136924: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.539: 38977949137014: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.563: 38977949161237: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.563: 38977949161394: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.563: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:09.563: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:09.582: 38977949180337: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.582: 38977949180482: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.582: 38977949180576: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.603: 38977949201303: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.603: 38977949201464: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.603: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.603: 38977949201651: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.604: 38977949201769: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.604: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.623: 38977949220949: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.623: 38977949221091: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.623: 38977949221160: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.646: 38977949243967: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.646: 38977949244183: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.646: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:09.646: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:09.665: 38977949263464: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.665: 38977949263617: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.665: 38977949263697: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.687: 38977949285696: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.688: 38977949285849: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.688: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.688: 38977949286028: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.688: 38977949286121: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.688: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.707: 38977949304783: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.707: 38977949304929: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.707: 38977949305015: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.727: 38977949325356: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.727: 38977949325491: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.727: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:09.727: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:09.746: 38977949344176: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.746: 38977949344316: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.746: 38977949344388: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.796: 38977949393941: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.796: 38977949394126: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.796: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.796: 38977949394309: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.796: 38977949394405: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.796: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.833: 38977949430813: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.833: 38977949430969: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.833: 38977949431048: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.871: 38977949469194: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.871: 38977949469343: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.871: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:09.871: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:09.903: 38977949501360: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.903: 38977949501492: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.903: 38977949501565: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:09.951: 38977949549051: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.951: 38977949549216: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:09.951: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:09.951: 38977949549403: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:09.951: 38977949549502: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:09.951: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:09.995: 38977949593564: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:09.995: 38977949593719: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:09.996: 38977949593804: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:10.017: 38977949615595: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:10.017: 38977949615753: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:10.018: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:10.018: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:10.036: 38977949634382: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:10.036: 38977949634538: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:10.036: 38977949634626: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:10.058: 38977949656122: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:10.058: 38977949656292: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:10.058: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:10.058: 38977949656485: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:10.058: 38977949656588: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:10.058: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:10.077: 38977949675163: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:10.077: 38977949675318: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:10.077: 38977949675400: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:10.100: 38977949698072: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:10.100: 38977949698214: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:10.100: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-image_device-DEBUG: 04:24:10.100: Image device reported finger status: on
(process:17747): libfprint-elan-DEBUG: 04:24:10.120: 38977949717834: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:10.120: 38977949717970: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:10.120: 38977949718058: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:10.141: 38977949739700: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:10.142: 38977949739863: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:10.142: [elan] CAPTURE_NUM_STATES entering state 3
(process:17747): libfprint-elan-DEBUG: 04:24:10.142: 38977949740025: ../libfprint/drivers/elan.c:203
(process:17747): libfprint-elan-DEBUG: 04:24:10.142: 38977949740125: ../libfprint/drivers/elan.c:118
(process:17747): libfprint-SSM-DEBUG: 04:24:10.142: [elan] CAPTURE_NUM_STATES entering state 1
(process:17747): libfprint-elan-DEBUG: 04:24:10.161: 38977949759688: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:10.162: 38977949759834: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:10.162: 38977949759905: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:10.182: 38977949780442: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:10.182: 38977949780569: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:10.182: [elan] CAPTURE_NUM_STATES entering state 2
(process:17747): libfprint-SSM-DEBUG: 04:24:10.182: [elan] CAPTURE_NUM_STATES completed successfully
(process:17747): libfprint-elan-DEBUG: 04:24:10.183: 38977949780846: ../libfprint/drivers/elan.c:586
(process:17747): libfprint-elan-DEBUG: 04:24:10.183: 38977949780927: ../libfprint/drivers/elan.c:315
(process:17747): libfprint-elan-DEBUG: 04:24:10.183: 38977949781020: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.184: 38977949782574: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.186: 38977949784658: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.188: 38977949786213: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.190: 38977949787767: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.191: 38977949789337: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.193: 38977949790902: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.194: 38977949792684: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.196: 38977949794259: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.198: 38977949795799: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.199: 38977949797386: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.201: 38977949798903: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.202: 38977949800474: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-elan-DEBUG: 04:24:10.204: 38977949802062: ../libfprint/drivers/elan.c:272
(process:17747): libfprint-assembling-DEBUG: 04:24:10.811: calc delta completed in 0.605651 secs
(process:17747): libfprint-assembling-DEBUG: 04:24:11.431: calc delta completed in 0.606023 secs
(process:17747): libfprint-assembling-DEBUG: 04:24:11.431: errors: 133465 rev: 143589
(process:17747): libfprint-assembling-DEBUG: 04:24:12.043: calc delta completed in 0.611470 secs
(process:17747): libfprint-assembling-DEBUG: 04:24:12.043: height is 225
(process:17747): libfprint-image_device-DEBUG: 04:24:12.044: Image device captured an image
(process:17747): libfprint-image_device-DEBUG: 04:24:12.044: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17747): libfprint-elan-DEBUG: 04:24:12.045: 38977951642854: ../libfprint/drivers/elan.c:960
(process:17747): libfprint-device-DEBUG: 04:24:12.045: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17747): libfprint-elan-DEBUG: 04:24:12.045: 38977951643108: ../libfprint/drivers/elan.c:507
(process:17747): libfprint-elan-DEBUG: 04:24:12.045: 38977951643182: ../libfprint/drivers/elan.c:100
(process:17747): libfprint-SSM-DEBUG: 04:24:12.045: [elan] STOP_CAPTURE_NUM_STATES entering state 0
(process:17747): libfprint-elan-DEBUG: 04:24:12.045: 38977951643427: ../libfprint/drivers/elan.c:466
(process:17747): libfprint-elan-DEBUG: 04:24:12.063: 38977951661404: ../libfprint/drivers/elan.c:346
(process:17747): libfprint-elan-DEBUG: 04:24:12.063: 38977951661573: ../libfprint/drivers/elan.c:366
(process:17747): libfprint-elan-DEBUG: 04:24:12.063: 38977951661663: ../libfprint/drivers/elan.c:379
(process:17747): libfprint-elan-DEBUG: 04:24:12.063: skipping read, not expecting anything
(process:17747): libfprint-elan-DEBUG: 04:24:12.064: 38977951661836: ../libfprint/drivers/elan.c:335
(process:17747): libfprint-SSM-DEBUG: 04:24:12.064: [elan] STOP_CAPTURE_NUM_STATES completed successfully
(process:17747): libfprint-elan-DEBUG: 04:24:12.064: 38977951662025: ../libfprint/drivers/elan.c:483
(process:17747): libfprint-device-DEBUG: 04:24:12.064: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17747): libfprint-image_device-DEBUG: 04:24:12.064: Image device reported finger status: off
(process:17747): libfprint-image_device-DEBUG: 04:24:12.064: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17747): libfprint-elan-DEBUG: 04:24:12.064: 38977951662561: ../libfprint/drivers/elan.c:960
(process:17747): libfprint-image_device-DEBUG: 04:24:12.064: Deactivating image device
(process:17747): libfprint-image_device-DEBUG: 04:24:12.065: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17747): libfprint-elan-DEBUG: 04:24:12.065: 38977951662925: ../libfprint/drivers/elan.c:960
(process:17747): libfprint-elan-DEBUG: 04:24:12.065: 38977951663027: ../libfprint/drivers/elan.c:975
(process:17747): libfprint-image_device-DEBUG: 04:24:12.065: Image device deactivation completed
(process:17747): libfprint-image_device-DEBUG: 04:24:12.065: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17747): libfprint-elan-DEBUG: 04:24:12.065: 38977951663381: ../libfprint/drivers/elan.c:960
(process:17747): libfprint-image-DEBUG: 04:24:12.162: Minutiae scan completed in 0.116014 secs
(process:17747): libfprint-device-DEBUG: 04:24:12.163: Device reported capture completion
(process:17747): libfprint-device-DEBUG: 04:24:12.163: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17747): libfprint-device-DEBUG: 04:24:12.164: Updated temperature model after 3.80 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17747): libfprint-elan-DEBUG: 04:24:12.165: 38977951763006: ../libfprint/drivers/elan.c:939
(process:17747): libfprint-elan-DEBUG: 04:24:12.165: 38977951763103: ../libfprint/drivers/elan.c:100
(process:17747): libfprint-image_device-DEBUG: 04:24:12.173: Image device close completed
(process:17747): libfprint-device-DEBUG: 04:24:12.173: Device reported close completion
(process:17747): libfprint-device-DEBUG: 04:24:12.177: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17747): libfprint-device-DEBUG: 04:24:12.177: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17743): DEBUG: 04:24:12.530: umockdev.vala:150: Removing test bed /tmp/umockdev.CXC9A2
(umockdev-run:17743): GLib-DEBUG: 04:24:12.576: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-lc2ayscp/capture.png and /<<PKGBUILDDIR>>/tests/elan-cobo/capture.png
==============================================================================
=================================== 95/116 ===================================
test: libfprint:drivers / elanmoc
start time: 04:24:09
duration: 3.59s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=elanmoc G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=88 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/elanmoc
----------------------------------- stdout -----------------------------------
** (umockdev-run:17761): DEBUG: 04:24:09.807: umockdev.vala:123: Created udev test bed /tmp/umockdev.4M4PB2
** (umockdev-run:17761): DEBUG: 04:24:09.812: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9
** (umockdev-run:17761): DEBUG: 04:24:09.826: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb)
** (umockdev-run:17761): DEBUG: 04:24:09.881: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.4M4PB2/dev/bus/usb/001/003
** (umockdev-run:17761): DEBUG: 04:24:09.881: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17761): DEBUG: 04:24:09.906: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17761): DEBUG: 04:24:09.945: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.4M4PB2/dev/bus/usb/001/001
** (umockdev-run:17761): DEBUG: 04:24:09.959: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17761): DEBUG: 04:24:09.964: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17761): GLib-DEBUG: 04:24:10.013: pidfd_open(17764) failed with error: Function not implemented
(process:17764): libfprint-context-DEBUG: 04:24:10.424: Initializing FpContext (libfprint version 1.94.6)
(process:17764): libfprint-elanmoc-DEBUG: 04:24:10.460: 38977950058646: ../libfprint/drivers/elanmoc/elanmoc.c:1150
(process:17764): libfprint-context-DEBUG: 04:24:10.462: No driver found for USB device 1D6B:0002
(process:17764): libfprint-device-DEBUG: 04:24:10.465: Device reported probe completion
(process:17764): libfprint-device-DEBUG: 04:24:10.466: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17764): libfprint-device-DEBUG: 04:24:10.470: Not updating temperature model, device can run continuously!
(process:17764): libfprint-SSM-DEBUG: 04:24:10.529: [elanmoc] DEV_INIT_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:10.530: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:10.552: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:10.587: [elanmoc] DEV_INIT_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:10.587: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:10.605: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:10.613: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:10.648: [elanmoc] DEV_INIT_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:10.648: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:10.661: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:10.679: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:10.715: elanmoc FW Version 8004
(process:17764): libfprint-SSM-DEBUG: 04:24:10.715: [elanmoc] DEV_INIT_STATES entering state 3
(process:17764): libfprint-SSM-DEBUG: 04:24:10.715: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:10.733: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:10.750: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:10.779: elanmoc last_read DIM 0x57(87) 0x6B(107)
(process:17764): libfprint-SSM-DEBUG: 04:24:10.779: [elanmoc] DEV_INIT_STATES entering state 4
(process:17764): libfprint-SSM-DEBUG: 04:24:10.779: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:10.796: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:10.818: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:10.848: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01)
(process:17764): libfprint-SSM-DEBUG: 04:24:10.849: [elanmoc] DEV_INIT_STATES completed successfully
(process:17764): libfprint-device-DEBUG: 04:24:10.849: Device reported open completion
(process:17764): libfprint-SSM-DEBUG: 04:24:10.849: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-device-DEBUG: 04:24:10.849: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17764): libfprint-device-DEBUG: 04:24:10.849: Not updating temperature model, device can run continuously!
(process:17764): libfprint-device-DEBUG: 04:24:10.859: Not updating temperature model, device can run continuously!
(process:17764): libfprint-SSM-DEBUG: 04:24:10.859: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:10.859: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:10.888: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:10.924: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01)
(process:17764): libfprint-SSM-DEBUG: 04:24:10.924: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:10.924: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:10.937: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:10.959: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:10.986: ##### Re-Enrollment Case! #####
(process:17764): libfprint-SSM-DEBUG: 04:24:10.986: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:10.987: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.000: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.017: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.049: Device reported enroll progress, reported 1 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.050: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:11.050: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.072: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.081: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.117: Device reported enroll progress, reported 2 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.118: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:11.118: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.131: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.148: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.175: Device reported enroll progress, reported 3 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.176: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:11.176: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.190: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.206: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.239: Device reported enroll progress, reported 4 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.239: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:11.239: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.252: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.269: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.302: Device reported enroll progress, reported 5 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.306: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:11.307: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.324: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.333: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.365: Device reported enroll progress, reported 6 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.365: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:11.366: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.383: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.396: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.433: Device reported enroll progress, reported 7 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.433: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:11.433: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.446: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.467: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.503: Device reported enroll progress, reported 7 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.504: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:11.504: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.513: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.535: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.565: Device reported enroll progress, reported 8 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.565: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:11.565: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.587: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.607: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.642: Device reported enroll progress, reported 8 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.643: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
(process:17764): libfprint-SSM-DEBUG: 04:24:11.643: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.660: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.674: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:11.706: Device reported enroll progress, reported 9 of 9 have been completed
(process:17764): libfprint-SSM-DEBUG: 04:24:11.714: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3
(process:17764): libfprint-SSM-DEBUG: 04:24:11.715: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.723: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.741: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:11.769: elanmoc_commit_cb success
(process:17764): libfprint-elanmoc-DEBUG: 04:24:11.769: Enrollment was successful!
(process:17764): libfprint-device-DEBUG: 04:24:11.769: Device reported enroll completion
(process:17764): libfprint-device-DEBUG: 04:24:11.769: Print for finger FP_FINGER_UNKNOWN enrolled
(process:17764): libfprint-SSM-DEBUG: 04:24:11.769: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.769: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-device-DEBUG: 04:24:11.769: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17764): libfprint-device-DEBUG: 04:24:11.770: Not updating temperature model, device can run continuously!
(process:17764): libfprint-SSM-DEBUG: 04:24:11.779: [elanmoc] MOC_LIST_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.779: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.805: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:11.833: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01)
(process:17764): libfprint-SSM-DEBUG: 04:24:11.834: [elanmoc] MOC_LIST_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:11.834: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.847: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.860: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:11.896: [elanmoc] MOC_LIST_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:11.896: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.905: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.917: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:11.950: [elanmoc] MOC_LIST_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:11.950: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:11.965: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:11.982: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.013: [elanmoc] MOC_LIST_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.014: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.023: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.040: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.074: [elanmoc] MOC_LIST_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.074: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.092: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.105: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.136: [elanmoc] MOC_LIST_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.136: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.149: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.166: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.224: [elanmoc] MOC_LIST_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.224: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.253: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.261: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.293: [elanmoc] MOC_LIST_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.293: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.314: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.338: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.369: [elanmoc] MOC_LIST_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.369: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.398: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.407: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.442: [elanmoc] MOC_LIST_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.442: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.458: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.474: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:12.519: Device reported listing completion
(process:17764): libfprint-SSM-DEBUG: 04:24:12.519: [elanmoc] MOC_LIST_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.519: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-device-DEBUG: 04:24:12.519: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17764): libfprint-device-DEBUG: 04:24:12.519: Not updating temperature model, device can run continuously!
(process:17764): libfprint-device-DEBUG: 04:24:12.527: Not updating temperature model, device can run continuously!
(process:17764): libfprint-SSM-DEBUG: 04:24:12.527: [elanmoc] IDENTIFY_NUM_STATES entering state 0
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.527: elanmoc elan_identify_run_state
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.527: elanmoc elan_identify_run_state IDENTIFY_SET_MODE
(process:17764): libfprint-SSM-DEBUG: 04:24:12.528: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.552: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.585: [elanmoc] IDENTIFY_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.585: elanmoc elan_identify_run_state
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.585: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER
(process:17764): libfprint-SSM-DEBUG: 04:24:12.585: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.602: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.611: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.645: Verify was successful! for user: 0 mesg_code: 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.645: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.663: [elanmoc] IDENTIFY_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.664: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.677: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.712: Verify/Identify successful for: FP1-00000000-0-00000000-nobody
(process:17764): libfprint-device-DEBUG: 04:24:12.714: Device reported verify result
(process:17764): libfprint-device-DEBUG: 04:24:12.714: Device reported verify completion
(process:17764): libfprint-SSM-DEBUG: 04:24:12.714: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-device-DEBUG: 04:24:12.715: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17764): libfprint-device-DEBUG: 04:24:12.715: Not updating temperature model, device can run continuously!
(process:17764): libfprint-device-DEBUG: 04:24:12.726: Not updating temperature model, device can run continuously!
(process:17764): libfprint-SSM-DEBUG: 04:24:12.727: [elanmoc] IDENTIFY_NUM_STATES entering state 0
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.727: elanmoc elan_identify_run_state
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.728: elanmoc elan_identify_run_state IDENTIFY_SET_MODE
(process:17764): libfprint-SSM-DEBUG: 04:24:12.728: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.756: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.790: [elanmoc] IDENTIFY_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.790: elanmoc elan_identify_run_state
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.790: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER
(process:17764): libfprint-SSM-DEBUG: 04:24:12.791: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.799: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.816: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.849: Verify was successful! for user: 0 mesg_code: 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.849: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.857: [elanmoc] IDENTIFY_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.857: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.874: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.906: Verify/Identify successful for: FP1-00000000-0-00000000-nobody
(process:17764): libfprint-device-DEBUG: 04:24:12.908: Device reported identify result
(process:17764): libfprint-device-DEBUG: 04:24:12.909: Device reported identify completion
(process:17764): libfprint-SSM-DEBUG: 04:24:12.909: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-device-DEBUG: 04:24:12.909: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17764): libfprint-device-DEBUG: 04:24:12.909: Not updating temperature model, device can run continuously!
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.919: Delete Finger, user_id = FP1-00000000-0-00000000-nobody!
(process:17764): libfprint-SSM-DEBUG: 04:24:12.920: [elanmoc] DELETE_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.920: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.939: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-device-DEBUG: 04:24:12.960: Device reported deletion completion
(process:17764): libfprint-SSM-DEBUG: 04:24:12.960: [elanmoc] DELETE_NUM_STATES completed successfully
(process:17764): libfprint-SSM-DEBUG: 04:24:12.960: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-device-DEBUG: 04:24:12.960: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(process:17764): libfprint-device-DEBUG: 04:24:12.960: Not updating temperature model, device can run continuously!
(process:17764): libfprint-elanmoc-DEBUG: 04:24:12.961: Elanmoc dev_exit
(process:17764): libfprint-SSM-DEBUG: 04:24:12.961: [elanmoc] DEV_EXIT_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.962: [elanmoc] FP_CMD_NUM_STATES entering state 0
(process:17764): libfprint-SSM-DEBUG: 04:24:12.979: [elanmoc] FP_CMD_NUM_STATES entering state 1
(process:17764): libfprint-SSM-DEBUG: 04:24:12.980: [elanmoc] DEV_EXIT_STATES completed successfully
(process:17764): libfprint-device-DEBUG: 04:24:12.988: Device reported close completion
(process:17764): libfprint-SSM-DEBUG: 04:24:12.993: [elanmoc] FP_CMD_NUM_STATES completed successfully
(process:17764): libfprint-device-DEBUG: 04:24:12.993: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17764): libfprint-device-DEBUG: 04:24:12.993: Not updating temperature model, device can run continuously!
enrolling
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 1, None, None, None)
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 2, None, None, None)
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 3, None, None, None)
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 4, None, None, None)
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 5, None, None, None)
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 6, None, None, None)
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 7, None, None, None)
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 8, None, None, None)
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
finger status: <flags 0 of type FPrint.FingerStatusFlags>
enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf6e02a08 (FpiDeviceElanmoc at 0x9160c0)>, 9, None, None, None)
enroll done
listing
listing done
verifying
verify done
async identifying
indentification_done: <FPrint.Print object at 0xf6e0f748 (FpPrint at 0x926218)> <FPrint.Print object at 0xf6e0f768 (FpPrint at 0x926250)>
deleting
delete done
** (umockdev-run:17761): DEBUG: 04:24:13.036: umockdev.vala:150: Removing test bed /tmp/umockdev.4M4PB2
(umockdev-run:17761): GLib-DEBUG: 04:24:13.092: unsetenv() is not thread-safe and should not be used after threads are created
==============================================================================
=================================== 96/116 ===================================
test: libfprint:drivers / upektc_img
start time: 04:24:13
duration: 3.73s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=upektc_img G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=147 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/upektc_img
----------------------------------- stdout -----------------------------------
** (umockdev-run:17787): DEBUG: 04:24:13.311: umockdev.vala:123: Created udev test bed /tmp/umockdev.QTN7A2
** (umockdev-run:17787): DEBUG: 04:24:13.312: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3
** (umockdev-run:17787): DEBUG: 04:24:13.338: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb)
** (umockdev-run:17787): DEBUG: 04:24:13.380: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.QTN7A2/dev/bus/usb/001/003
** (umockdev-run:17787): DEBUG: 04:24:13.382: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1
** (umockdev-run:17787): DEBUG: 04:24:13.402: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb)
** (umockdev-run:17787): DEBUG: 04:24:13.435: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.QTN7A2/dev/bus/usb/001/002
** (umockdev-run:17787): DEBUG: 04:24:13.436: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1
** (umockdev-run:17787): DEBUG: 04:24:13.455: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb)
** (umockdev-run:17787): DEBUG: 04:24:13.487: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.QTN7A2/dev/bus/usb/001/001
** (umockdev-run:17787): DEBUG: 04:24:13.489: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0
** (umockdev-run:17787): DEBUG: 04:24:13.503: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci)
(umockdev-run:17787): GLib-DEBUG: 04:24:13.538: pidfd_open(17790) failed with error: Function not implemented
(process:17790): libfprint-context-DEBUG: 04:24:13.898: Initializing FpContext (libfprint version 1.94.6)
(process:17790): libfprint-context-DEBUG: 04:24:13.922: No driver found for USB device 8087:0020
(process:17790): libfprint-context-DEBUG: 04:24:13.922: No driver found for USB device 1D6B:0002
(process:17790): libfprint-device-DEBUG: 04:24:13.924: Device reported probe completion
(process:17790): libfprint-device-DEBUG: 04:24:13.925: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17790): libfprint-device-DEBUG: 04:24:13.925: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17790): libfprint-image_device-DEBUG: 04:24:13.963: Image device open completed
(process:17790): libfprint-device-DEBUG: 04:24:13.963: Device reported open completion
(process:17790): libfprint-device-DEBUG: 04:24:13.963: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17790): libfprint-device-DEBUG: 04:24:13.964: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17790): libfprint-device-DEBUG: 04:24:13.965: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17790): libfprint-image_device-DEBUG: 04:24:13.966: Activating image device
(process:17790): libfprint-image_device-DEBUG: 04:24:13.966: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17790): libfprint-SSM-DEBUG: 04:24:13.966: [upektc_img] ACTIVATE_NUM_STATES entering state 0
(process:17790): libfprint-SSM-DEBUG: 04:24:13.988: [upektc_img] ACTIVATE_NUM_STATES entering state 1
(process:17790): libfprint-SSM-DEBUG: 04:24:14.010: [upektc_img] ACTIVATE_NUM_STATES entering state 2
(process:17790): libfprint-SSM-DEBUG: 04:24:14.031: [upektc_img] ACTIVATE_NUM_STATES entering state 3
(process:17790): libfprint-SSM-DEBUG: 04:24:14.053: [upektc_img] ACTIVATE_NUM_STATES entering state 4
(process:17790): libfprint-device-DEBUG: 04:24:14.069: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17790): libfprint-SSM-DEBUG: 04:24:14.073: [upektc_img] ACTIVATE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:14.094: [upektc_img] ACTIVATE_NUM_STATES entering state 6
(process:17790): libfprint-SSM-DEBUG: 04:24:14.112: [upektc_img] ACTIVATE_NUM_STATES entering state 7
(process:17790): libfprint-SSM-DEBUG: 04:24:14.132: [upektc_img] ACTIVATE_NUM_STATES entering state 8
(process:17790): libfprint-SSM-DEBUG: 04:24:14.150: [upektc_img] ACTIVATE_NUM_STATES entering state 9
(process:17790): libfprint-SSM-DEBUG: 04:24:14.171: [upektc_img] ACTIVATE_NUM_STATES entering state 10
(process:17790): libfprint-SSM-DEBUG: 04:24:14.189: [upektc_img] ACTIVATE_NUM_STATES entering state 11
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.210: Sensor type : TCS4x, width x height: 192 x 512
(process:17790): libfprint-SSM-DEBUG: 04:24:14.210: [upektc_img] ACTIVATE_NUM_STATES completed successfully
(process:17790): libfprint-image_device-DEBUG: 04:24:14.210: Image device activation completed
(process:17790): libfprint-image_device-DEBUG: 04:24:14.210: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17790): libfprint-image_device-DEBUG: 04:24:14.210: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17790): libfprint-device-DEBUG: 04:24:14.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17790): libfprint-SSM-DEBUG: 04:24:14.211: [upektc_img] CAPTURE_NUM_STATES entering state 0
(process:17790): libfprint-SSM-DEBUG: 04:24:14.229: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.249: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.249: 18th byte is 0c
(process:17790): libfprint-SSM-DEBUG: 04:24:14.250: [upektc_img] CAPTURE_NUM_STATES entering state 3
(process:17790): libfprint-SSM-DEBUG: 04:24:14.268: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.288: request completed, len: 0040
(process:17790): libfprint-SSM-DEBUG: 04:24:14.288: [upektc_img] CAPTURE_NUM_STATES entering state 4
(process:17790): libfprint-SSM-DEBUG: 04:24:14.307: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.326: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.327: 18th byte is 00
(process:17790): libfprint-device-DEBUG: 04:24:14.327: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17790): libfprint-SSM-DEBUG: 04:24:14.327: [upektc_img] CAPTURE_NUM_STATES entering state 3
(process:17790): libfprint-SSM-DEBUG: 04:24:14.345: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.365: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.365: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.365: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:14.365: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.385: request completed, len: 07c4
(process:17790): libfprint-image_device-DEBUG: 04:24:14.385: Image device reported finger status: on
(process:17790): libfprint-image_device-DEBUG: 04:24:14.385: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17790): libfprint-SSM-DEBUG: 04:24:14.385: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:14.404: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.425: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.425: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.425: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:14.425: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.445: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:14.445: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:14.472: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.500: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.500: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.501: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:14.501: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.534: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:14.534: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:14.560: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.588: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.588: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.588: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:14.588: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.615: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:14.615: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:14.641: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.672: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.673: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.673: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:14.673: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.704: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:14.705: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:14.734: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.766: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.766: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.766: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:14.766: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.793: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:14.793: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:14.819: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.852: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.852: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.852: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:14.852: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.880: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:14.880: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:14.910: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.942: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.942: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.943: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:14.943: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:14.971: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:14.971: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:14.997: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.025: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.026: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.026: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.034: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.059: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.059: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.089: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.114: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.114: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.114: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.114: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.142: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.142: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.170: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.203: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.203: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.203: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.203: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.233: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.233: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.259: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.287: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.287: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.287: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.287: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.316: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.316: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.338: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.361: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.361: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.361: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.361: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.381: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.381: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.400: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.421: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.421: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.421: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.421: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.440: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.441: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.459: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.480: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.480: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.480: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.480: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.501: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.501: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.519: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.540: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.540: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.540: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.540: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.560: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.560: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.578: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.601: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.601: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.601: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.601: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.622: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.622: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.640: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.660: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.660: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.660: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.660: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.679: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.679: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.696: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.716: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.716: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.716: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.716: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.736: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.736: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.756: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.777: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.777: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.777: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.777: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.797: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.798: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.816: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.836: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.836: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.836: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.836: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.857: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.857: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.875: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.895: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.896: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.896: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.896: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.916: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.916: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.936: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.955: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.955: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.955: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:15.955: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:15.976: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:15.976: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:15.994: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.013: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.014: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.014: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:16.014: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.034: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:16.034: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:16.054: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.074: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.074: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.074: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:16.074: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.094: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:16.094: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:16.112: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.131: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.131: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.132: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:16.132: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.151: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:16.151: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:16.170: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.190: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.190: response_size is 2052, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.190: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:16.190: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.209: request completed, len: 07c4
(process:17790): libfprint-SSM-DEBUG: 04:24:16.209: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17790): libfprint-SSM-DEBUG: 04:24:16.227: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.249: request completed, len: 0040
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.249: response_size is 186, actual_length is 64
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.249: Waiting for rest of transfer
(process:17790): libfprint-SSM-DEBUG: 04:24:16.249: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.270: request completed, len: 007a
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.270: Image size is 55296
(process:17790): libfprint-image_device-DEBUG: 04:24:16.270: Image device captured an image
(process:17790): libfprint-image_device-DEBUG: 04:24:16.271: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17790): libfprint-device-DEBUG: 04:24:16.271: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17790): libfprint-device-DEBUG: 04:24:16.271: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17790): libfprint-image_device-DEBUG: 04:24:16.271: Image device reported finger status: off
(process:17790): libfprint-image_device-DEBUG: 04:24:16.271: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17790): libfprint-image_device-DEBUG: 04:24:16.271: Deactivating image device
(process:17790): libfprint-image_device-DEBUG: 04:24:16.271: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17790): libfprint-SSM-DEBUG: 04:24:16.272: [upektc_img] CAPTURE_NUM_STATES completed successfully
(process:17790): libfprint-SSM-DEBUG: 04:24:16.272: [upektc_img] DEACTIVATE_NUM_STATES entering state 0
(process:17790): libfprint-SSM-DEBUG: 04:24:16.289: [upektc_img] DEACTIVATE_NUM_STATES entering state 1
(process:17790): libfprint-SSM-DEBUG: 04:24:16.308: [upektc_img] DEACTIVATE_NUM_STATES completed successfully
(process:17790): libfprint-upektc_img-DEBUG: 04:24:16.308: Deactivate completed
(process:17790): libfprint-image_device-DEBUG: 04:24:16.308: Image device deactivation completed
(process:17790): libfprint-image_device-DEBUG: 04:24:16.309: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17790): libfprint-image-DEBUG: 04:24:16.331: Minutiae scan completed in 0.056972 secs
(process:17790): libfprint-device-DEBUG: 04:24:16.332: Device reported capture completion
(process:17790): libfprint-device-DEBUG: 04:24:16.332: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17790): libfprint-device-DEBUG: 04:24:16.332: Updated temperature model after 2.26 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17790): libfprint-image_device-DEBUG: 04:24:16.338: Image device close completed
(process:17790): libfprint-device-DEBUG: 04:24:16.339: Device reported close completion
(process:17790): libfprint-device-DEBUG: 04:24:16.343: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17790): libfprint-device-DEBUG: 04:24:16.343: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17787): DEBUG: 04:24:16.638: umockdev.vala:150: Removing test bed /tmp/umockdev.QTN7A2
(umockdev-run:17787): GLib-DEBUG: 04:24:16.691: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-k03fop8n/capture.png and /<<PKGBUILDDIR>>/tests/upektc_img/capture.png
==============================================================================
=================================== 97/116 ===================================
test: libfprint:drivers / synaptics
start time: 04:24:12
duration: 5.11s
result: exit status 0
command: MALLOC_PERTURB_=96 G_DEBUG=fatal-warnings LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf NO_AT_BRIDGE=1 FP_DRIVERS_WHITELIST=synaptics MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/synaptics
----------------------------------- stdout -----------------------------------
** (umockdev-run:17779): DEBUG: 04:24:12.952: umockdev.vala:123: Created udev test bed /tmp/umockdev.LUELB2
** (umockdev-run:17779): DEBUG: 04:24:12.953: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9
** (umockdev-run:17779): DEBUG: 04:24:12.970: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb)
** (umockdev-run:17779): DEBUG: 04:24:13.008: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.LUELB2/dev/bus/usb/001/004
** (umockdev-run:17779): DEBUG: 04:24:13.010: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17779): DEBUG: 04:24:13.024: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17779): DEBUG: 04:24:13.065: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.LUELB2/dev/bus/usb/001/001
** (umockdev-run:17779): DEBUG: 04:24:13.079: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17779): DEBUG: 04:24:13.084: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17779): GLib-DEBUG: 04:24:13.123: pidfd_open(17782) failed with error: Function not implemented
(process:17782): libfprint-context-DEBUG: 04:24:13.516: Initializing FpContext (libfprint version 1.94.6)
(process:17782): libfprint-context-DEBUG: 04:24:13.548: No driver found for USB device 1D6B:0002
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.555: 38977953153131: ../libfprint/drivers/synaptics/synaptics.c:1231
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.636: Build Time: 1596608839
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.636: Build Num: 3273255
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.636: Version: 10.1
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.636: Target: 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.636: Product: 65
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.636: sequence number is 1
(process:17782): libfprint-SSM-DEBUG: 04:24:13.636: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:13.663: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:13.705: Device reported probe completion
(process:17782): libfprint-SSM-DEBUG: 04:24:13.705: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(process:17782): libfprint-device-DEBUG: 04:24:13.705: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17782): libfprint-device-DEBUG: 04:24:13.714: Not updating temperature model, device can run continuously!
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.740: 38977953338063: ../libfprint/drivers/synaptics/synaptics.c:1391
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.744: sequence number is 2
(process:17782): libfprint-SSM-DEBUG: 04:24:13.745: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:13.788: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:13.819: Device reported open completion
(process:17782): libfprint-SSM-DEBUG: 04:24:13.819: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(process:17782): libfprint-device-DEBUG: 04:24:13.820: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17782): libfprint-device-DEBUG: 04:24:13.820: Not updating temperature model, device can run continuously!
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.821: clear all prints in database
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.821: sequence number is 3
(process:17782): libfprint-SSM-DEBUG: 04:24:13.821: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:13.849: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.886: Deleting All Enrolled Users is 0% complete
(process:17782): libfprint-SSM-DEBUG: 04:24:13.886: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.907: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:13.907: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:13.928: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:13.928: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:13.928: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.949: Deleting All Enrolled Users is 100% complete
(process:17782): libfprint-SSM-DEBUG: 04:24:13.949: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:13.973: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:13.974: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:13.992: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:13.993: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:13.993: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.021: Successfully deleted all enrolled user
(process:17782): libfprint-device-DEBUG: 04:24:14.022: Device reported deletion completion
(process:17782): libfprint-SSM-DEBUG: 04:24:14.022: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(process:17782): libfprint-device-DEBUG: 04:24:14.022: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17782): libfprint-device-DEBUG: 04:24:14.022: Not updating temperature model, device can run continuously!
(process:17782): libfprint-device-DEBUG: 04:24:14.028: Not updating temperature model, device can run continuously!
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.028: 38977953626551: ../libfprint/drivers/synaptics/synaptics.c:1002
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.029: user_id: FP1-00000000-0-00000000-nobody, finger: 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.029: sequence number is 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.029: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.055: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:14.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.092: Place Finger on the Sensor!
(process:17782): libfprint-SSM-DEBUG: 04:24:14.092: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.121: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:14.122: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:14.152: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.152: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.152: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:14.177: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.178: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.178: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:14.178: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.211: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:14.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:14.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.238: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.238: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.267: Fingerprint image capture complete!
(process:17782): libfprint-SSM-DEBUG: 04:24:14.267: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.296: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:14.296: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:14.327: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.327: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.327: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:14.356: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.356: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.356: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:14.356: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.389: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:14.390: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:14.416: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.416: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.417: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.446: Enrollment is 12 %
(process:17782): libfprint-device-DEBUG: 04:24:14.446: Device reported enroll progress, reported 1 of 8 have been completed
(process:17782): libfprint-SSM-DEBUG: 04:24:14.446: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.483: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:14.483: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:14.510: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.510: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.510: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:14.539: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.539: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.539: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:14.539: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.568: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:14.568: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:14.603: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.603: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.603: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.632: Fingerprint image capture complete!
(process:17782): libfprint-SSM-DEBUG: 04:24:14.632: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.661: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:14.661: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:14.692: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.692: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.692: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:14.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.725: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.725: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:14.725: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.755: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:14.755: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:14.788: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.788: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.788: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.822: Enrollment is 25 %
(process:17782): libfprint-device-DEBUG: 04:24:14.822: Device reported enroll progress, reported 2 of 8 have been completed
(process:17782): libfprint-SSM-DEBUG: 04:24:14.822: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.851: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:14.852: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:14.886: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.887: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.887: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:14.916: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.916: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.916: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:14.916: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:14.949: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:14.949: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:14.977: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:14.977: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:14.977: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.010: Fingerprint image capture complete!
(process:17782): libfprint-SSM-DEBUG: 04:24:15.010: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.046: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.046: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.078: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.079: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.079: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.108: Enrollment is 37 %
(process:17782): libfprint-device-DEBUG: 04:24:15.108: Device reported enroll progress, reported 3 of 8 have been completed
(process:17782): libfprint-SSM-DEBUG: 04:24:15.108: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.138: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.138: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.165: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.165: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.165: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:15.198: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.198: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.198: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:15.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.232: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.232: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:15.296: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.296: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.296: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:15.296: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.325: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.325: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.349: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.349: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.350: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.387: Fingerprint image capture complete!
(process:17782): libfprint-SSM-DEBUG: 04:24:15.387: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.417: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.417: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.444: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.444: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.444: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:15.477: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.477: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.477: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:15.477: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.514: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.514: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.541: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.541: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.541: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.570: Enrollment is 50 %
(process:17782): libfprint-device-DEBUG: 04:24:15.570: Device reported enroll progress, reported 4 of 8 have been completed
(process:17782): libfprint-SSM-DEBUG: 04:24:15.570: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.599: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.600: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.630: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.631: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.631: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:15.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.660: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.660: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:15.660: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.700: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.701: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.722: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.723: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.723: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.752: Fingerprint image capture complete!
(process:17782): libfprint-SSM-DEBUG: 04:24:15.752: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.781: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.782: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.813: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.813: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.813: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:15.842: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.842: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.842: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:15.843: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.881: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.881: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.904: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.904: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.904: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.933: Enrollment is 62 %
(process:17782): libfprint-device-DEBUG: 04:24:15.933: Device reported enroll progress, reported 5 of 8 have been completed
(process:17782): libfprint-SSM-DEBUG: 04:24:15.934: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:15.967: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:15.967: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:15.994: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:15.994: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:15.994: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:16.027: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.027: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.027: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:16.028: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.057: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.057: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.084: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.084: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.084: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.117: Fingerprint image capture complete!
(process:17782): libfprint-SSM-DEBUG: 04:24:16.117: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.150: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.151: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:16.215: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.215: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.215: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:16.215: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.244: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.275: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.276: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.276: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.313: Enrollment is 62 %
(process:17782): libfprint-device-DEBUG: 04:24:16.313: Device reported enroll progress, reported 5 of 8 have been completed
(process:17782): libfprint-SSM-DEBUG: 04:24:16.313: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.346: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.346: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.377: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.377: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.377: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:16.406: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.406: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.406: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:16.406: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.440: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.441: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.471: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.471: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.472: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.504: Fingerprint image capture complete!
(process:17782): libfprint-SSM-DEBUG: 04:24:16.505: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.538: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.542: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.569: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.569: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.569: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.602: Enrollment is 75 %
(process:17782): libfprint-device-DEBUG: 04:24:16.602: Device reported enroll progress, reported 6 of 8 have been completed
(process:17782): libfprint-SSM-DEBUG: 04:24:16.602: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.632: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.632: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.668: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.668: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.668: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:16.688: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.688: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.688: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:16.688: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.708: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.708: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.726: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.726: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.726: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:16.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.745: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.745: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:16.745: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.765: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.765: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.782: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.782: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.782: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.802: Fingerprint image capture complete!
(process:17782): libfprint-SSM-DEBUG: 04:24:16.802: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.823: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.823: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.840: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.840: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.840: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:16.860: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.860: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.860: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:16.860: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.878: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.879: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.896: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.896: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.896: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.915: Enrollment is 87 %
(process:17782): libfprint-device-DEBUG: 04:24:16.915: Device reported enroll progress, reported 7 of 8 have been completed
(process:17782): libfprint-SSM-DEBUG: 04:24:16.915: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.937: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.937: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:16.954: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:16.954: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:16.954: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:16.975: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.975: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.975: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:16.976: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:16.997: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:16.997: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:17.016: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:17.016: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.016: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.037: Fingerprint image capture complete!
(process:17782): libfprint-SSM-DEBUG: 04:24:17.037: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.057: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:17.057: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:17.074: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:17.074: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.074: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:17.095: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.095: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.095: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:17.095: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.117: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:17.117: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:17.134: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:17.134: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.134: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.154: Enrollment is 100 %
(process:17782): libfprint-device-DEBUG: 04:24:17.154: Device reported enroll progress, reported 8 of 8 have been completed
(process:17782): libfprint-SSM-DEBUG: 04:24:17.155: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.177: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:17.177: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:17.196: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:17.196: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.196: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:17.215: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.215: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.215: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:17.215: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.236: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:17.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:17.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:17.254: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.254: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:17.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.274: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.274: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:17.274: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.293: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:17.293: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:17.312: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:17.312: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.312: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.332: Enrollment was successful!
(process:17782): libfprint-device-DEBUG: 04:24:17.332: Device reported enroll completion
(process:17782): libfprint-device-DEBUG: 04:24:17.332: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17782): libfprint-device-DEBUG: 04:24:17.332: Print for finger FP_FINGER_UNKNOWN enrolled
(process:17782): libfprint-SSM-DEBUG: 04:24:17.332: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(process:17782): libfprint-device-DEBUG: 04:24:17.333: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17782): libfprint-device-DEBUG: 04:24:17.333: Not updating temperature model, device can run continuously!
(process:17782): libfprint-device-DEBUG: 04:24:17.335: Not updating temperature model, device can run continuously!
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.335: data is 0x21e3c28
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.336: 38977956933770: ../libfprint/drivers/synaptics/synaptics.c:636
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.336: sequence number is 5
(process:17782): libfprint-SSM-DEBUG: 04:24:17.336: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.353: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:17.374: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.374: Place Finger on the Sensor!
(process:17782): libfprint-SSM-DEBUG: 04:24:17.374: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.384: got suspend request
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.397: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:17.397: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.400: got resume request
(process:17782): libfprint-SSM-DEBUG: 04:24:17.401: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6
(process:17782): libfprint-SSM-DEBUG: 04:24:17.401: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.421: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:17.421: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:17.439: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:17.440: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.440: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:17.459: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.460: Finger is now on the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.460: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:17.460: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.483: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:17.483: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:17.500: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:17.500: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.500: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.520: Fingerprint image capture complete!
(process:17782): libfprint-SSM-DEBUG: 04:24:17.520: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.540: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:17.540: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:17.559: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:17.559: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.559: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-device-DEBUG: 04:24:17.579: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.579: Finger is now off the sensor
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.579: Received message with 0 sequence number 0x91, ignoring!
(process:17782): libfprint-SSM-DEBUG: 04:24:17.579: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.599: interrupt transfer done
(process:17782): libfprint-SSM-DEBUG: 04:24:17.599: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:17782): libfprint-SSM-DEBUG: 04:24:17.617: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:17782): libfprint-SSM-DEBUG: 04:24:17.617: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.617: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.637: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000
(process:17782): libfprint-device-DEBUG: 04:24:17.637: Device reported verify result
(process:17782): libfprint-device-DEBUG: 04:24:17.637: Device reported verify completion
(process:17782): libfprint-device-DEBUG: 04:24:17.637: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17782): libfprint-SSM-DEBUG: 04:24:17.637: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(process:17782): libfprint-device-DEBUG: 04:24:17.638: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17782): libfprint-device-DEBUG: 04:24:17.638: Not updating temperature model, device can run continuously!
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.639: data is 0x21e3c28
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.639: 38977957237498: ../libfprint/drivers/synaptics/synaptics.c:1111
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.639: sequence number is 6
(process:17782): libfprint-SSM-DEBUG: 04:24:17.639: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.657: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.677: Successfully deleted enrolled user
(process:17782): libfprint-device-DEBUG: 04:24:17.677: Device reported deletion completion
(process:17782): libfprint-SSM-DEBUG: 04:24:17.678: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(process:17782): libfprint-device-DEBUG: 04:24:17.678: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(process:17782): libfprint-device-DEBUG: 04:24:17.678: Not updating temperature model, device can run continuously!
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.679: 38977957277371: ../libfprint/drivers/synaptics/synaptics.c:1412
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.679: sequence number is 7
(process:17782): libfprint-SSM-DEBUG: 04:24:17.679: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:17782): libfprint-SSM-DEBUG: 04:24:17.697: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:17782): libfprint-synaptics-DEBUG: 04:24:17.725: Fingerprint sensor ready to be powered down
(process:17782): libfprint-device-DEBUG: 04:24:17.725: Device reported close completion
(process:17782): libfprint-SSM-DEBUG: 04:24:17.729: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(process:17782): libfprint-device-DEBUG: 04:24:17.730: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17782): libfprint-device-DEBUG: 04:24:17.730: Not updating temperature model, device can run continuously!
enrolling
enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf72219a8 (FpiDeviceSynaptics at 0x225e0e8)>, 1, None, None, None)
enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf72219a8 (FpiDeviceSynaptics at 0x225e0e8)>, 2, None, None, None)
enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf72219a8 (FpiDeviceSynaptics at 0x225e0e8)>, 3, None, None, None)
enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf72219a8 (FpiDeviceSynaptics at 0x225e0e8)>, 4, None, None, None)
enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf72219a8 (FpiDeviceSynaptics at 0x225e0e8)>, 5, None, None, None)
enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf72219a8 (FpiDeviceSynaptics at 0x225e0e8)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0))
enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf72219a8 (FpiDeviceSynaptics at 0x225e0e8)>, 6, None, None, None)
enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf72219a8 (FpiDeviceSynaptics at 0x225e0e8)>, 7, None, None, None)
enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf72219a8 (FpiDeviceSynaptics at 0x225e0e8)>, 8, None, None, None)
enroll done
verifying
verify done
deleting
delete done
** (umockdev-run:17779): DEBUG: 04:24:17.777: umockdev.vala:150: Removing test bed /tmp/umockdev.LUELB2
(umockdev-run:17779): GLib-DEBUG: 04:24:17.815: unsetenv() is not thread-safe and should not be used after threads are created
----------------------------------- stderr -----------------------------------
libusb: warning [libusb_exit] device 1.1 still referenced
==============================================================================
=================================== 98/116 ===================================
test: libfprint:drivers / upektc_img-tcs1s
start time: 04:24:16
duration: 3.67s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DRIVERS_WHITELIST=upektc_img G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=159 G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/upektc_img-tcs1s
----------------------------------- stdout -----------------------------------
** (umockdev-run:17805): DEBUG: 04:24:17.129: umockdev.vala:123: Created udev test bed /tmp/umockdev.YMACB2
** (umockdev-run:17805): DEBUG: 04:24:17.134: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2
** (umockdev-run:17805): DEBUG: 04:24:17.188: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb)
** (umockdev-run:17805): DEBUG: 04:24:17.226: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.YMACB2/dev/bus/usb/003/004
** (umockdev-run:17805): DEBUG: 04:24:17.227: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3
** (umockdev-run:17805): DEBUG: 04:24:17.269: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb)
** (umockdev-run:17805): DEBUG: 04:24:17.306: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.YMACB2/dev/bus/usb/003/001
** (umockdev-run:17805): DEBUG: 04:24:17.307: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4
** (umockdev-run:17805): DEBUG: 04:24:17.334: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci)
** (umockdev-run:17805): DEBUG: 04:24:17.371: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1
** (umockdev-run:17805): DEBUG: 04:24:17.382: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci)
(umockdev-run:17805): GLib-DEBUG: 04:24:17.434: pidfd_open(17808) failed with error: Function not implemented
(process:17808): libfprint-context-DEBUG: 04:24:17.809: Initializing FpContext (libfprint version 1.94.6)
(process:17808): libfprint-context-DEBUG: 04:24:17.830: No driver found for USB device 1D6B:0002
(process:17808): libfprint-device-DEBUG: 04:24:17.832: Device reported probe completion
(process:17808): libfprint-device-DEBUG: 04:24:17.833: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17808): libfprint-device-DEBUG: 04:24:17.834: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17808): libfprint-image_device-DEBUG: 04:24:17.852: Image device open completed
(process:17808): libfprint-device-DEBUG: 04:24:17.852: Device reported open completion
(process:17808): libfprint-device-DEBUG: 04:24:17.853: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17808): libfprint-device-DEBUG: 04:24:17.853: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17808): libfprint-device-DEBUG: 04:24:17.854: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17808): libfprint-image_device-DEBUG: 04:24:17.855: Activating image device
(process:17808): libfprint-image_device-DEBUG: 04:24:17.855: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17808): libfprint-SSM-DEBUG: 04:24:17.855: [upektc_img] ACTIVATE_NUM_STATES entering state 0
(process:17808): libfprint-SSM-DEBUG: 04:24:17.881: [upektc_img] ACTIVATE_NUM_STATES entering state 1
(process:17808): libfprint-SSM-DEBUG: 04:24:17.903: [upektc_img] ACTIVATE_NUM_STATES entering state 2
(process:17808): libfprint-SSM-DEBUG: 04:24:17.920: [upektc_img] ACTIVATE_NUM_STATES entering state 3
(process:17808): libfprint-SSM-DEBUG: 04:24:17.942: [upektc_img] ACTIVATE_NUM_STATES entering state 4
(process:17808): libfprint-device-DEBUG: 04:24:17.956: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17808): libfprint-SSM-DEBUG: 04:24:17.960: [upektc_img] ACTIVATE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:17.980: [upektc_img] ACTIVATE_NUM_STATES entering state 6
(process:17808): libfprint-SSM-DEBUG: 04:24:17.997: [upektc_img] ACTIVATE_NUM_STATES entering state 7
(process:17808): libfprint-SSM-DEBUG: 04:24:18.017: [upektc_img] ACTIVATE_NUM_STATES entering state 8
(process:17808): libfprint-SSM-DEBUG: 04:24:18.034: [upektc_img] ACTIVATE_NUM_STATES entering state 9
(process:17808): libfprint-SSM-DEBUG: 04:24:18.054: [upektc_img] ACTIVATE_NUM_STATES entering state 10
(process:17808): libfprint-SSM-DEBUG: 04:24:18.085: [upektc_img] ACTIVATE_NUM_STATES entering state 11
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.116: Sensor type : TCS1x, width x height: 256 x 360
(process:17808): libfprint-SSM-DEBUG: 04:24:18.116: [upektc_img] ACTIVATE_NUM_STATES completed successfully
(process:17808): libfprint-image_device-DEBUG: 04:24:18.116: Image device activation completed
(process:17808): libfprint-image_device-DEBUG: 04:24:18.116: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17808): libfprint-image_device-DEBUG: 04:24:18.116: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17808): libfprint-device-DEBUG: 04:24:18.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17808): libfprint-SSM-DEBUG: 04:24:18.116: [upektc_img] CAPTURE_NUM_STATES entering state 0
(process:17808): libfprint-SSM-DEBUG: 04:24:18.137: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.154: request completed, len: 0000
(process:17808): libfprint-SSM-DEBUG: 04:24:18.155: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.175: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.175: 18th byte is 0c
(process:17808): libfprint-SSM-DEBUG: 04:24:18.175: [upektc_img] CAPTURE_NUM_STATES entering state 3
(process:17808): libfprint-SSM-DEBUG: 04:24:18.194: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.210: request completed, len: 0000
(process:17808): libfprint-SSM-DEBUG: 04:24:18.210: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.231: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.231: 18th byte is 13
(process:17808): libfprint-SSM-DEBUG: 04:24:18.231: [upektc_img] CAPTURE_NUM_STATES entering state 3
(process:17808): libfprint-SSM-DEBUG: 04:24:18.251: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.266: request completed, len: 0000
(process:17808): libfprint-SSM-DEBUG: 04:24:18.266: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.290: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.290: 18th byte is 00
(process:17808): libfprint-device-DEBUG: 04:24:18.290: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17808): libfprint-SSM-DEBUG: 04:24:18.290: [upektc_img] CAPTURE_NUM_STATES entering state 3
(process:17808): libfprint-SSM-DEBUG: 04:24:18.310: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.326: request completed, len: 0000
(process:17808): libfprint-SSM-DEBUG: 04:24:18.326: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.347: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.347: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.347: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.347: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.370: request completed, len: 07c4
(process:17808): libfprint-image_device-DEBUG: 04:24:18.370: Image device reported finger status: on
(process:17808): libfprint-image_device-DEBUG: 04:24:18.371: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17808): libfprint-SSM-DEBUG: 04:24:18.371: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:18.389: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.409: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.409: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.409: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.409: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.429: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:18.429: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:18.448: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.468: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.468: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.468: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.468: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.490: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:18.490: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:18.508: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.528: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.528: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.528: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.528: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.548: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:18.548: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:18.566: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.587: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.587: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.587: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.587: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.610: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:18.610: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:18.627: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.647: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.647: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.647: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.647: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.671: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:18.671: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:18.691: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.714: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.714: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.714: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.715: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.737: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:18.737: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:18.754: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.775: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.775: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.775: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.775: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.796: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:18.796: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:18.828: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.848: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.848: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.848: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.849: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.870: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:18.870: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:18.889: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.909: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.909: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.909: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.910: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.932: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:18.932: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:18.950: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.972: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.972: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.972: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:18.972: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:18.993: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:18.993: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.013: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.036: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.036: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.036: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.036: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.056: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.057: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.075: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.096: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.096: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.096: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.096: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.117: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.117: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.136: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.157: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.157: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.157: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.157: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.178: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.178: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.196: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.216: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.216: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.216: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.216: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.237: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.237: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.255: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.275: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.275: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.275: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.275: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.294: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.295: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.315: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.335: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.335: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.335: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.335: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.355: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.356: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.374: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.395: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.395: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.395: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.395: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.415: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.415: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.437: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.458: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.458: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.458: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.458: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.478: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.479: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.497: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.517: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.517: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.517: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.517: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.537: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.537: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.556: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.580: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.580: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.581: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.581: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.601: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.601: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.619: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.639: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.639: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.639: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.640: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.661: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.661: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.680: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.701: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.702: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.702: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.702: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.722: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.722: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.740: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.760: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.760: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.760: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.760: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.780: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.780: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.797: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.821: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.821: response_size is 2052, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.821: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.821: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.842: request completed, len: 07c4
(process:17808): libfprint-SSM-DEBUG: 04:24:19.842: [upektc_img] CAPTURE_NUM_STATES entering state 5
(process:17808): libfprint-SSM-DEBUG: 04:24:19.859: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.879: request completed, len: 0040
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.879: response_size is 814, actual_length is 64
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.879: Waiting for rest of transfer
(process:17808): libfprint-SSM-DEBUG: 04:24:19.879: [upektc_img] CAPTURE_NUM_STATES entering state 1
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.899: request completed, len: 02ee
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.899: Image size is 51840
(process:17808): libfprint-image_device-DEBUG: 04:24:19.899: Image device captured an image
(process:17808): libfprint-image_device-DEBUG: 04:24:19.900: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17808): libfprint-device-DEBUG: 04:24:19.900: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17808): libfprint-device-DEBUG: 04:24:19.900: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17808): libfprint-image_device-DEBUG: 04:24:19.901: Image device reported finger status: off
(process:17808): libfprint-image_device-DEBUG: 04:24:19.901: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17808): libfprint-image_device-DEBUG: 04:24:19.901: Deactivating image device
(process:17808): libfprint-image_device-DEBUG: 04:24:19.901: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17808): libfprint-SSM-DEBUG: 04:24:19.901: [upektc_img] CAPTURE_NUM_STATES completed successfully
(process:17808): libfprint-SSM-DEBUG: 04:24:19.901: [upektc_img] DEACTIVATE_NUM_STATES entering state 0
(process:17808): libfprint-SSM-DEBUG: 04:24:19.919: [upektc_img] DEACTIVATE_NUM_STATES entering state 1
(process:17808): libfprint-SSM-DEBUG: 04:24:19.940: [upektc_img] DEACTIVATE_NUM_STATES completed successfully
(process:17808): libfprint-upektc_img-DEBUG: 04:24:19.940: Deactivate completed
(process:17808): libfprint-image_device-DEBUG: 04:24:19.940: Image device deactivation completed
(process:17808): libfprint-image_device-DEBUG: 04:24:19.940: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17808): libfprint-image-DEBUG: 04:24:20.027: Minutiae scan completed in 0.124819 secs
(process:17808): libfprint-device-DEBUG: 04:24:20.028: Device reported capture completion
(process:17808): libfprint-device-DEBUG: 04:24:20.028: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17808): libfprint-device-DEBUG: 04:24:20.028: Updated temperature model after 2.07 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17808): libfprint-image_device-DEBUG: 04:24:20.035: Image device close completed
(process:17808): libfprint-device-DEBUG: 04:24:20.036: Device reported close completion
(process:17808): libfprint-device-DEBUG: 04:24:20.040: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17808): libfprint-device-DEBUG: 04:24:20.040: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17805): DEBUG: 04:24:20.338: umockdev.vala:150: Removing test bed /tmp/umockdev.YMACB2
(umockdev-run:17805): GLib-DEBUG: 04:24:20.394: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-1i4gwx3u/capture.png and /<<PKGBUILDDIR>>/tests/upektc_img-tcs1s/capture.png
==============================================================================
=================================== 99/116 ===================================
test: libfprint:drivers / uru4000-msv2
start time: 04:24:17
duration: 3.02s
result: exit status 0
command: G_DEBUG=fatal-warnings MALLOC_PERTURB_=91 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf NO_AT_BRIDGE=1 FP_DEVICE_EMULATION=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_DRIVERS_WHITELIST=uru4000 FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/uru4000-msv2
----------------------------------- stdout -----------------------------------
** (umockdev-run:17815): DEBUG: 04:24:18.117: umockdev.vala:123: Created udev test bed /tmp/umockdev.IHQBB2
** (umockdev-run:17815): DEBUG: 04:24:18.126: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10
** (umockdev-run:17815): DEBUG: 04:24:18.146: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb)
** (umockdev-run:17815): DEBUG: 04:24:18.176: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.IHQBB2/dev/bus/usb/001/047
** (umockdev-run:17815): DEBUG: 04:24:18.177: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17815): DEBUG: 04:24:18.199: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17815): DEBUG: 04:24:18.240: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.IHQBB2/dev/bus/usb/001/001
** (umockdev-run:17815): DEBUG: 04:24:18.241: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17815): DEBUG: 04:24:18.246: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17815): GLib-DEBUG: 04:24:18.290: pidfd_open(17818) failed with error: Function not implemented
(process:17818): libfprint-context-DEBUG: 04:24:18.763: Initializing FpContext (libfprint version 1.94.6)
(process:17818): libfprint-context-DEBUG: 04:24:18.795: No driver found for USB device 1D6B:0002
(process:17818): libfprint-device-DEBUG: 04:24:18.797: Device reported probe completion
(process:17818): libfprint-device-DEBUG: 04:24:18.798: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17818): libfprint-device-DEBUG: 04:24:18.806: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17818): GLib-DEBUG: 04:24:18.842: setenv()/putenv() are not thread-safe and should not be used after threads are created
(process:17818): libfprint-image_device-DEBUG: 04:24:18.852: Image device open completed
(process:17818): libfprint-device-DEBUG: 04:24:18.853: Device reported open completion
(process:17818): libfprint-device-DEBUG: 04:24:18.853: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17818): libfprint-device-DEBUG: 04:24:18.853: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17818): libfprint-device-DEBUG: 04:24:18.855: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17818): libfprint-image_device-DEBUG: 04:24:18.855: Activating image device
(process:17818): libfprint-image_device-DEBUG: 04:24:18.855: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17818): libfprint-SSM-DEBUG: 04:24:18.930: [uru4000] INIT_NUM_STATES entering state 0
(process:17818): libfprint-uru4000-DEBUG: 04:24:18.930: read 1 regs at 7
(process:17818): libfprint-device-DEBUG: 04:24:18.961: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17818): libfprint-uru4000-DEBUG: 04:24:18.965: reg value 3
(process:17818): libfprint-SSM-DEBUG: 04:24:18.966: [uru4000] INIT_NUM_STATES entering state 1
(process:17818): libfprint-SSM-DEBUG: 04:24:18.966: [uru4000] INIT_NUM_STATES entering state 3
(process:17818): libfprint-uru4000-DEBUG: 04:24:18.970: set 83
(process:17818): libfprint-SSM-DEBUG: 04:24:18.995: [uru4000] INIT_NUM_STATES entering state 4
(process:17818): libfprint-SSM-DEBUG: 04:24:18.996: [uru4000] POWERUP_NUM_STATES entering state 0
(process:17818): libfprint-SSM-DEBUG: 04:24:18.996: [uru4000] POWERUP_NUM_STATES entering state 1
(process:17818): libfprint-uru4000-DEBUG: 04:24:18.996: set 03
(process:17818): libfprint-SSM-DEBUG: 04:24:19.026: [uru4000] POWERUP_NUM_STATES entering state 2
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.026: read 1 regs at 7
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.058: reg value 83
(process:17818): libfprint-SSM-DEBUG: 04:24:19.058: [uru4000] POWERUP_NUM_STATES entering state 3
(process:17818): libfprint-SSM-DEBUG: 04:24:19.058: [uru4000] POWERUP_NUM_STATES entering state 4
(process:17818): libfprint-SSM-DEBUG: 04:24:19.069: [uru4000] POWERUP_NUM_STATES entering state 5
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.069: 38977958667011: ../libfprint/drivers/uru4000.c:291
(process:17818): libfprint-SSM-DEBUG: 04:24:19.124: [uru4000] POWERUP_NUM_STATES entering state 6
(process:17818): libfprint-SSM-DEBUG: 04:24:19.124: [uru4000] POWERUP_NUM_STATES entering state 1
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.125: set 03
(process:17818): libfprint-SSM-DEBUG: 04:24:19.158: [uru4000] POWERUP_NUM_STATES entering state 2
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.158: read 1 regs at 7
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.188: reg value 3
(process:17818): libfprint-SSM-DEBUG: 04:24:19.188: [uru4000] POWERUP_NUM_STATES entering state 3
(process:17818): libfprint-SSM-DEBUG: 04:24:19.188: [uru4000] POWERUP_NUM_STATES completed successfully
(process:17818): libfprint-SSM-DEBUG: 04:24:19.188: [uru4000] INIT_NUM_STATES entering state 5
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.220: recv irq type 56aa
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.220: late scanpwr interrupt
(process:17818): libfprint-SSM-DEBUG: 04:24:19.220: [uru4000] INIT_NUM_STATES entering state 6
(process:17818): libfprint-SSM-DEBUG: 04:24:19.221: [uru4000] INIT_NUM_STATES entering state 7
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.221: read 16 regs at f0
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.250: reg value 50
(process:17818): libfprint-SSM-DEBUG: 04:24:19.250: [uru4000] INIT_NUM_STATES entering state 8
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.250: Versions 0059 and 0034
(process:17818): libfprint-SSM-DEBUG: 04:24:19.250: [uru4000] INIT_NUM_STATES completed successfully
(process:17818): libfprint-image_device-DEBUG: 04:24:19.250: Image device activation completed
(process:17818): libfprint-image_device-DEBUG: 04:24:19.250: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17818): libfprint-image_device-DEBUG: 04:24:19.250: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.250: wait finger on
(process:17818): libfprint-device-DEBUG: 04:24:19.264: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.311: recv irq type 0101
(process:17818): libfprint-device-DEBUG: 04:24:19.311: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17818): libfprint-image_device-DEBUG: 04:24:19.311: Image device reported finger status: on
(process:17818): libfprint-image_device-DEBUG: 04:24:19.312: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.312: starting capture
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.312: Image encryption seed: 1374298404
(process:17818): libfprint-SSM-DEBUG: 04:24:19.312: [uru4000] IMAGING_NUM_STATES entering state 0
(process:17818): libfprint-SSM-DEBUG: 04:24:19.371: [uru4000] IMAGING_NUM_STATES entering state 1
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.371: hw header lines 289
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.371: dev2: 10849
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.371: image seems to be encrypted
(process:17818): libfprint-SSM-DEBUG: 04:24:19.393: [uru4000] IMAGING_NUM_STATES entering state 2
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.393: read 4 regs at 34
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.424: reg value 7b
(process:17818): libfprint-SSM-DEBUG: 04:24:19.425: [uru4000] IMAGING_NUM_STATES entering state 3
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.425: encryption id 05 -> key db896f5f
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.425: 0 02 67
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.425: decoding 67 lines
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.425: 1 00 1
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.425: skipping 1 lines
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.425: 2 02 49
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.425: decoding 49 lines
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.426: 3 01 1
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.426: skipping 1 lines
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.426: 4 00 1
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.426: skipping 1 lines
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.426: 5 02 49
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.426: decoding 49 lines
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.426: 6 00 1
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.426: skipping 1 lines
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.426: 7 02 121
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.426: decoding 121 lines
(process:17818): libfprint-SSM-DEBUG: 04:24:19.427: [uru4000] IMAGING_NUM_STATES entering state 4
(process:17818): libfprint-image_device-DEBUG: 04:24:19.428: Image device captured an image
(process:17818): libfprint-image_device-DEBUG: 04:24:19.428: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17818): libfprint-device-DEBUG: 04:24:19.428: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17818): libfprint-SSM-DEBUG: 04:24:19.429: [uru4000] IMAGING_NUM_STATES completed successfully
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.429: await finger off
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.495: recv irq type 0200
(process:17818): libfprint-device-DEBUG: 04:24:19.495: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17818): libfprint-image_device-DEBUG: 04:24:19.495: Image device reported finger status: off
(process:17818): libfprint-image_device-DEBUG: 04:24:19.495: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17818): libfprint-image_device-DEBUG: 04:24:19.495: Deactivating image device
(process:17818): libfprint-image_device-DEBUG: 04:24:19.496: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.496: deactivating
(process:17818): libfprint-uru4000-DEBUG: 04:24:19.548: cancelled
(process:17818): libfprint-image_device-DEBUG: 04:24:19.548: Image device deactivation completed
(process:17818): libfprint-image_device-DEBUG: 04:24:19.548: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17818): libfprint-image-DEBUG: 04:24:19.667: Minutiae scan completed in 0.237661 secs
(process:17818): libfprint-device-DEBUG: 04:24:19.668: Device reported capture completion
(process:17818): libfprint-device-DEBUG: 04:24:19.668: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17818): libfprint-device-DEBUG: 04:24:19.668: Updated temperature model after 0.71 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17818): libfprint-image_device-DEBUG: 04:24:19.687: Image device close completed
(process:17818): libfprint-device-DEBUG: 04:24:19.687: Device reported close completion
(process:17818): libfprint-device-DEBUG: 04:24:19.692: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17818): libfprint-device-DEBUG: 04:24:19.692: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17815): DEBUG: 04:24:20.618: umockdev.vala:150: Removing test bed /tmp/umockdev.IHQBB2
(umockdev-run:17815): GLib-DEBUG: 04:24:20.659: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-5u8hvsqh/capture.png and /<<PKGBUILDDIR>>/tests/uru4000-msv2/capture.png
==============================================================================
================================== 100/116 ===================================
test: libfprint:drivers / uru4000-4500
start time: 04:24:20
duration: 2.95s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MALLOC_PERTURB_=162 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_DRIVERS_WHITELIST=uru4000 FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/uru4000-4500
----------------------------------- stdout -----------------------------------
** (umockdev-run:17827): DEBUG: 04:24:20.849: umockdev.vala:123: Created udev test bed /tmp/umockdev.KF1IB2
** (umockdev-run:17827): DEBUG: 04:24:20.858: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10
** (umockdev-run:17827): DEBUG: 04:24:20.869: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb)
** (umockdev-run:17827): DEBUG: 04:24:20.904: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.KF1IB2/dev/bus/usb/001/050
** (umockdev-run:17827): DEBUG: 04:24:20.905: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17827): DEBUG: 04:24:20.923: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17827): DEBUG: 04:24:20.965: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.KF1IB2/dev/bus/usb/001/001
** (umockdev-run:17827): DEBUG: 04:24:20.966: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17827): DEBUG: 04:24:20.980: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17827): GLib-DEBUG: 04:24:21.018: pidfd_open(17832) failed with error: Function not implemented
(process:17832): libfprint-context-DEBUG: 04:24:21.451: Initializing FpContext (libfprint version 1.94.6)
(process:17832): libfprint-context-DEBUG: 04:24:21.483: No driver found for USB device 1D6B:0002
(process:17832): libfprint-device-DEBUG: 04:24:21.490: Device reported probe completion
(process:17832): libfprint-device-DEBUG: 04:24:21.491: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17832): libfprint-device-DEBUG: 04:24:21.491: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17832): GLib-DEBUG: 04:24:21.558: setenv()/putenv() are not thread-safe and should not be used after threads are created
(process:17832): libfprint-image_device-DEBUG: 04:24:21.568: Image device open completed
(process:17832): libfprint-device-DEBUG: 04:24:21.568: Device reported open completion
(process:17832): libfprint-device-DEBUG: 04:24:21.569: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17832): libfprint-device-DEBUG: 04:24:21.569: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17832): libfprint-device-DEBUG: 04:24:21.571: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17832): libfprint-image_device-DEBUG: 04:24:21.572: Activating image device
(process:17832): libfprint-image_device-DEBUG: 04:24:21.572: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17832): libfprint-SSM-DEBUG: 04:24:21.610: [uru4000] INIT_NUM_STATES entering state 0
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.610: read 1 regs at 7
(process:17832): libfprint-device-DEBUG: 04:24:21.681: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.682: reg value 1
(process:17832): libfprint-SSM-DEBUG: 04:24:21.683: [uru4000] INIT_NUM_STATES entering state 1
(process:17832): libfprint-SSM-DEBUG: 04:24:21.683: [uru4000] INIT_NUM_STATES entering state 3
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.683: set 81
(process:17832): libfprint-SSM-DEBUG: 04:24:21.730: [uru4000] INIT_NUM_STATES entering state 4
(process:17832): libfprint-SSM-DEBUG: 04:24:21.730: [uru4000] POWERUP_NUM_STATES entering state 0
(process:17832): libfprint-SSM-DEBUG: 04:24:21.730: [uru4000] POWERUP_NUM_STATES entering state 1
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.730: set 01
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.817: recv irq type 56aa
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.817: early scanpwr interrupt
(process:17832): libfprint-SSM-DEBUG: 04:24:21.834: [uru4000] POWERUP_NUM_STATES entering state 2
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.835: read 1 regs at 7
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.867: reg value 1
(process:17832): libfprint-SSM-DEBUG: 04:24:21.868: [uru4000] POWERUP_NUM_STATES entering state 3
(process:17832): libfprint-SSM-DEBUG: 04:24:21.868: [uru4000] POWERUP_NUM_STATES completed successfully
(process:17832): libfprint-SSM-DEBUG: 04:24:21.868: [uru4000] INIT_NUM_STATES entering state 5
(process:17832): libfprint-SSM-DEBUG: 04:24:21.868: [uru4000] INIT_NUM_STATES entering state 6
(process:17832): libfprint-SSM-DEBUG: 04:24:21.868: [uru4000] INIT_NUM_STATES entering state 7
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.868: read 16 regs at f0
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.906: reg value 1a
(process:17832): libfprint-SSM-DEBUG: 04:24:21.910: [uru4000] INIT_NUM_STATES entering state 8
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.910: Versions 0010 and 0115
(process:17832): libfprint-SSM-DEBUG: 04:24:21.910: [uru4000] INIT_NUM_STATES completed successfully
(process:17832): libfprint-image_device-DEBUG: 04:24:21.910: Image device activation completed
(process:17832): libfprint-image_device-DEBUG: 04:24:21.910: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17832): libfprint-image_device-DEBUG: 04:24:21.910: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.911: wait finger on
(process:17832): libfprint-device-DEBUG: 04:24:21.928: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17832): libfprint-uru4000-DEBUG: 04:24:21.979: recv irq type 56aa
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.017: recv irq type 56aa
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.054: recv irq type 0101
(process:17832): libfprint-device-DEBUG: 04:24:22.054: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17832): libfprint-image_device-DEBUG: 04:24:22.055: Image device reported finger status: on
(process:17832): libfprint-image_device-DEBUG: 04:24:22.055: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.055: starting capture
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.055: Image encryption seed: 1374298404
(process:17832): libfprint-SSM-DEBUG: 04:24:22.055: [uru4000] IMAGING_NUM_STATES entering state 0
(process:17832): libfprint-SSM-DEBUG: 04:24:22.128: [uru4000] IMAGING_NUM_STATES entering state 1
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.128: hw header lines 289
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.128: dev2: 11240
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.128: image seems to be encrypted
(process:17832): libfprint-SSM-DEBUG: 04:24:22.163: [uru4000] IMAGING_NUM_STATES entering state 2
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.163: read 4 regs at 34
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.191: reg value f2
(process:17832): libfprint-SSM-DEBUG: 04:24:22.191: [uru4000] IMAGING_NUM_STATES entering state 3
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.191: encryption id 00 -> key 544409d6
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.191: 0 02 72
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.192: decoding 72 lines
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.192: 1 00 1
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.192: skipping 1 lines
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.192: 2 02 49
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.192: decoding 49 lines
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.192: 3 01 1
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.193: skipping 1 lines
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.193: 4 00 1
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.193: skipping 1 lines
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.193: 5 02 49
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.193: decoding 49 lines
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.193: 6 00 1
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.193: skipping 1 lines
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.193: 7 02 116
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.193: decoding 116 lines
(process:17832): libfprint-SSM-DEBUG: 04:24:22.199: [uru4000] IMAGING_NUM_STATES entering state 4
(process:17832): libfprint-image_device-DEBUG: 04:24:22.200: Image device captured an image
(process:17832): libfprint-image_device-DEBUG: 04:24:22.200: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17832): libfprint-device-DEBUG: 04:24:22.200: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17832): libfprint-SSM-DEBUG: 04:24:22.200: [uru4000] IMAGING_NUM_STATES completed successfully
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.201: await finger off
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.267: recv irq type 0200
(process:17832): libfprint-device-DEBUG: 04:24:22.267: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17832): libfprint-image_device-DEBUG: 04:24:22.267: Image device reported finger status: off
(process:17832): libfprint-image_device-DEBUG: 04:24:22.267: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17832): libfprint-image_device-DEBUG: 04:24:22.267: Deactivating image device
(process:17832): libfprint-image_device-DEBUG: 04:24:22.267: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.267: deactivating
(process:17832): libfprint-uru4000-DEBUG: 04:24:22.316: cancelled
(process:17832): libfprint-image_device-DEBUG: 04:24:22.316: Image device deactivation completed
(process:17832): libfprint-image_device-DEBUG: 04:24:22.316: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17832): libfprint-image-DEBUG: 04:24:22.331: Minutiae scan completed in 0.125035 secs
(process:17832): libfprint-device-DEBUG: 04:24:22.339: Device reported capture completion
(process:17832): libfprint-device-DEBUG: 04:24:22.339: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17832): libfprint-device-DEBUG: 04:24:22.339: Updated temperature model after 0.66 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17832): libfprint-image_device-DEBUG: 04:24:22.355: Image device close completed
(process:17832): libfprint-device-DEBUG: 04:24:22.355: Device reported close completion
(process:17832): libfprint-device-DEBUG: 04:24:22.360: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17832): libfprint-device-DEBUG: 04:24:22.360: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17827): DEBUG: 04:24:23.234: umockdev.vala:150: Removing test bed /tmp/umockdev.KF1IB2
(umockdev-run:17827): GLib-DEBUG: 04:24:23.280: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-n5fh2xce/capture.png and /<<PKGBUILDDIR>>/tests/uru4000-4500/capture.png
----------------------------------- stderr -----------------------------------
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
==============================================================================
================================== 101/116 ===================================
test: libfprint:drivers / vfs0050
start time: 04:24:20
duration: 5.14s
result: exit status 0
command: G_DEBUG=fatal-warnings FP_DRIVERS_WHITELIST=vfs0050 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf NO_AT_BRIDGE=1 FP_DEVICE_EMULATION=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=58 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/vfs0050
----------------------------------- stdout -----------------------------------
** (umockdev-run:17834): DEBUG: 04:24:21.098: umockdev.vala:123: Created udev test bed /tmp/umockdev.BCABB2
** (umockdev-run:17834): DEBUG: 04:24:21.098: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9
** (umockdev-run:17834): DEBUG: 04:24:21.115: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb)
** (umockdev-run:17834): DEBUG: 04:24:21.152: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.BCABB2/dev/bus/usb/001/004
** (umockdev-run:17834): DEBUG: 04:24:21.153: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17834): DEBUG: 04:24:21.167: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17834): DEBUG: 04:24:21.193: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.BCABB2/dev/bus/usb/001/001
** (umockdev-run:17834): DEBUG: 04:24:21.195: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17834): DEBUG: 04:24:21.208: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17834): GLib-GIO-DEBUG: 04:24:21.240: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
(umockdev-run:17834): GLib-DEBUG: 04:24:21.358: pidfd_open(17837) failed with error: Function not implemented
(process:17837): libfprint-context-DEBUG: 04:24:21.721: Initializing FpContext (libfprint version 1.94.6)
(process:17837): libfprint-context-DEBUG: 04:24:21.757: No driver found for USB device 1D6B:0002
(process:17837): libfprint-device-DEBUG: 04:24:21.760: Device reported probe completion
(process:17837): libfprint-device-DEBUG: 04:24:21.761: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17837): libfprint-device-DEBUG: 04:24:21.761: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17837): libfprint-SSM-DEBUG: 04:24:21.806: [vfs0050] SSM_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:21.841: [vfs0050] SSM_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:21.871: [vfs0050] SSM_STATES entering state 2
(process:17837): libfprint-SSM-DEBUG: 04:24:21.880: [vfs0050] SSM_STATES entering state 3
(process:17837): libfprint-SSM-DEBUG: 04:24:21.881: [vfs0050] SUBSM1_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:21.916: [vfs0050] SUBSM1_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:21.949: [vfs0050] SUBSM1_STATES entering state 2
(process:17837): libfprint-SSM-DEBUG: 04:24:21.976: [vfs0050] SUBSM1_STATES completed successfully
(process:17837): libfprint-SSM-DEBUG: 04:24:21.976: [vfs0050] SSM_STATES entering state 4
(process:17837): libfprint-SSM-DEBUG: 04:24:21.977: [vfs0050] SUBSM2_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:22.007: [vfs0050] SUBSM2_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:22.038: [vfs0050] SUBSM2_STATES entering state 2
(process:17837): libfprint-SSM-DEBUG: 04:24:22.074: [vfs0050] SUBSM2_STATES entering state 3
(process:17837): libfprint-SSM-DEBUG: 04:24:22.110: [vfs0050] SUBSM2_STATES entering state 4
(process:17837): libfprint-SSM-DEBUG: 04:24:22.135: [vfs0050] SUBSM2_STATES entering state 5
(process:17837): libfprint-SSM-DEBUG: 04:24:22.164: [vfs0050] SUBSM2_STATES entering state 6
(process:17837): libfprint-SSM-DEBUG: 04:24:22.164: [vfs0050] SUBSM1_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:22.194: [vfs0050] SUBSM1_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:22.231: [vfs0050] SUBSM1_STATES entering state 2
(process:17837): libfprint-SSM-DEBUG: 04:24:22.259: [vfs0050] SUBSM1_STATES completed successfully
(process:17837): libfprint-SSM-DEBUG: 04:24:22.260: [vfs0050] SUBSM2_STATES completed successfully
(process:17837): libfprint-SSM-DEBUG: 04:24:22.260: [vfs0050] SSM_STATES entering state 5
(process:17837): libfprint-SSM-DEBUG: 04:24:22.260: [vfs0050] SSM_STATES completed successfully
(process:17837): libfprint-image_device-DEBUG: 04:24:22.260: Image device open completed
(process:17837): libfprint-device-DEBUG: 04:24:22.260: Device reported open completion
(process:17837): libfprint-device-DEBUG: 04:24:22.260: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17837): libfprint-device-DEBUG: 04:24:22.261: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17837): libfprint-device-DEBUG: 04:24:22.262: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17837): libfprint-image_device-DEBUG: 04:24:22.263: Activating image device
(process:17837): libfprint-image_device-DEBUG: 04:24:22.263: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17837): libfprint-SSM-DEBUG: 04:24:22.263: [vfs0050] SSM_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:22.286: [vfs0050] SSM_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:22.318: [vfs0050] SSM_STATES entering state 2
(process:17837): libfprint-SSM-DEBUG: 04:24:22.337: [vfs0050] SSM_STATES entering state 3
(process:17837): libfprint-SSM-DEBUG: 04:24:22.337: [vfs0050] SUBSM1_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:22.367: [vfs0050] SUBSM1_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:22.402: [vfs0050] SUBSM1_STATES entering state 2
(process:17837): libfprint-device-DEBUG: 04:24:22.423: Updated temperature model after 0.16 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17837): libfprint-SSM-DEBUG: 04:24:22.425: [vfs0050] SUBSM1_STATES completed successfully
(process:17837): libfprint-SSM-DEBUG: 04:24:22.426: [vfs0050] SSM_STATES entering state 4
(process:17837): libfprint-SSM-DEBUG: 04:24:22.426: [vfs0050] SUBSM2_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:22.455: [vfs0050] SUBSM2_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:22.480: [vfs0050] SUBSM2_STATES entering state 2
(process:17837): libfprint-SSM-DEBUG: 04:24:22.505: [vfs0050] SUBSM2_STATES entering state 3
(process:17837): libfprint-SSM-DEBUG: 04:24:22.532: [vfs0050] SUBSM2_STATES entering state 4
(process:17837): libfprint-SSM-DEBUG: 04:24:22.556: [vfs0050] SUBSM2_STATES entering state 5
(process:17837): libfprint-SSM-DEBUG: 04:24:22.580: [vfs0050] SUBSM2_STATES entering state 6
(process:17837): libfprint-SSM-DEBUG: 04:24:22.580: [vfs0050] SUBSM1_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:22.605: [vfs0050] SUBSM1_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:22.640: [vfs0050] SUBSM1_STATES entering state 2
(process:17837): libfprint-SSM-DEBUG: 04:24:22.663: [vfs0050] SUBSM1_STATES completed successfully
(process:17837): libfprint-SSM-DEBUG: 04:24:22.663: [vfs0050] SUBSM2_STATES completed successfully
(process:17837): libfprint-SSM-DEBUG: 04:24:22.663: [vfs0050] SSM_STATES entering state 5
(process:17837): libfprint-SSM-DEBUG: 04:24:22.663: [vfs0050] SUBSM2_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:22.688: [vfs0050] SUBSM2_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:22.713: [vfs0050] SUBSM2_STATES entering state 2
(process:17837): libfprint-SSM-DEBUG: 04:24:22.738: [vfs0050] SUBSM2_STATES entering state 3
(process:17837): libfprint-SSM-DEBUG: 04:24:22.761: [vfs0050] SUBSM2_STATES entering state 4
(process:17837): libfprint-SSM-DEBUG: 04:24:22.790: [vfs0050] SUBSM2_STATES entering state 5
(process:17837): libfprint-SSM-DEBUG: 04:24:22.810: [vfs0050] SUBSM2_STATES entering state 6
(process:17837): libfprint-SSM-DEBUG: 04:24:22.810: [vfs0050] SUBSM2_STATES completed successfully
(process:17837): libfprint-SSM-DEBUG: 04:24:22.814: [vfs0050] SSM_STATES entering state 6
(process:17837): libfprint-image_device-DEBUG: 04:24:22.814: Image device activation completed
(process:17837): libfprint-image_device-DEBUG: 04:24:22.814: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17837): libfprint-image_device-DEBUG: 04:24:22.814: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17837): libfprint-device-DEBUG: 04:24:22.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17837): libfprint-SSM-DEBUG: 04:24:22.822: [vfs0050] SSM_STATES entering state 7
(process:17837): libfprint-SSM-DEBUG: 04:24:22.837: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-device-DEBUG: 04:24:22.837: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17837): libfprint-image_device-DEBUG: 04:24:22.838: Image device reported finger status: on
(process:17837): libfprint-image_device-DEBUG: 04:24:22.838: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17837): libfprint-SSM-DEBUG: 04:24:22.869: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:22.902: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:22.930: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:22.963: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:22.990: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.018: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.050: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.077: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.105: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.132: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.167: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.195: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.222: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.250: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.278: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.310: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.338: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.365: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.392: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.419: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.451: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.478: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.510: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.542: [vfs0050] SSM_STATES entering state 8
(process:17837): libfprint-SSM-DEBUG: 04:24:23.565: [vfs0050] SSM_STATES entering state 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.575: 1694838263575739
(process:17837): libfprint-assembling-DEBUG: 04:24:23.576: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.576: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.576: 2
(process:17837): libfprint-assembling-DEBUG: 04:24:23.577: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.577: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.577: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:23.578: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.578: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:23.579: 5
(process:17837): libfprint-assembling-DEBUG: 04:24:23.579: 3
(process:17837): libfprint-assembling-DEBUG: 04:24:23.579: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.579: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:23.580: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.580: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.580: 2
(process:17837): libfprint-assembling-DEBUG: 04:24:23.581: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.581: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.581: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.582: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.582: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.582: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.582: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.582: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.582: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.582: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.582: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.582: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.582: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 5
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 3
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.583: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 2
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.584: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.585: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.586: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.586: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.586: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.586: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.593: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.594: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:23.594: 95
(process:17837): libfprint-assembling-DEBUG: 04:24:23.594: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:23.595: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.595: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.596: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.596: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:23.596: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.597: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:23.597: 88
(process:17837): libfprint-assembling-DEBUG: 04:24:23.597: 86
(process:17837): libfprint-assembling-DEBUG: 04:24:23.598: 84
(process:17837): libfprint-assembling-DEBUG: 04:24:23.598: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.598: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.600: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.600: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.600: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.601: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:23.601: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:23.601: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:23.602: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:23.606: 64
(process:17837): libfprint-assembling-DEBUG: 04:24:23.606: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:23.606: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:23.606: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 2
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 2
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 3
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.607: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.608: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 88
(process:17837): libfprint-assembling-DEBUG: 04:24:23.609: 86
(process:17837): libfprint-assembling-DEBUG: 04:24:23.610: 84
(process:17837): libfprint-assembling-DEBUG: 04:24:23.610: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:23.610: 95
(process:17837): libfprint-assembling-DEBUG: 04:24:23.615: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:23.615: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:23.617: 95
(process:17837): libfprint-assembling-DEBUG: 04:24:23.617: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:23.622: 91
(process:17837): libfprint-assembling-DEBUG: 04:24:23.622: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:23.623: 87
(process:17837): libfprint-assembling-DEBUG: 04:24:23.623: 85
(process:17837): libfprint-assembling-DEBUG: 04:24:23.623: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:23.624: 87
(process:17837): libfprint-assembling-DEBUG: 04:24:23.624: 85
(process:17837): libfprint-assembling-DEBUG: 04:24:23.624: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:23.625: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:23.625: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:23.626: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:23.627: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:23.627: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:23.627: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:23.628: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:23.628: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:23.628: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:23.629: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:23.629: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:23.629: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 69
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 64
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 64
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:23.630: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.631: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:23.632: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 48
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.633: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.634: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.634: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.644: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.644: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:23.645: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:23.647: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:23.647: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:23.647: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:23.648: 48
(process:17837): libfprint-assembling-DEBUG: 04:24:23.648: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:23.648: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:23.649: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:23.649: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:23.649: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.654: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.654: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.656: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.656: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.657: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.657: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:23.657: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:23.658: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:23.658: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:23.658: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:23.659: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.660: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.661: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.661: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:23.661: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:23.662: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.663: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:23.664: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.665: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.666: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.666: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.666: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.675: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.677: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.678: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.678: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.678: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.679: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.679: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.679: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.680: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.680: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.680: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.681: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.681: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.688: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.688: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.689: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.690: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.690: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.690: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.691: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.691: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.691: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.691: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.691: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.691: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.692: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.693: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.694: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.695: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.696: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.697: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.698: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.698: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.711: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.711: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.712: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.712: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.712: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.714: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.720: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.720: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.720: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.721: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.721: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.721: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.722: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.722: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.724: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.724: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.724: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.725: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.725: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.725: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.726: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.726: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.726: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.727: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.727: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.727: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.729: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.729: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.730: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.730: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.730: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.731: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.731: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.731: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.732: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.733: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.734: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.742: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.743: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.743: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.743: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.743: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.743: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.743: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.743: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.743: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.743: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.744: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.745: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.746: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.747: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.748: 91
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 86
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.749: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.750: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.750: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.750: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.759: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.760: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.760: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.760: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.761: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:23.761: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:23.761: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.762: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:23.766: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.768: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.769: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.769: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:23.770: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:23.770: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.770: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:23.771: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:23.771: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.771: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.772: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.772: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.772: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.774: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.774: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.774: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.775: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.775: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.775: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.776: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.776: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.776: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.777: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.778: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.779: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.779: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.779: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.779: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.780: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.780: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.780: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.781: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.786: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.786: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.787: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.787: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.787: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.787: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.787: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.787: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.787: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.787: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.787: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.788: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.789: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.790: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.790: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.797: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.800: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.800: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.800: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.801: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.801: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.801: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.802: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.802: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.802: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.803: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.803: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.805: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.805: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.806: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.806: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.806: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.807: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.807: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.807: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.807: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.807: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.807: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.807: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.807: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.807: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.807: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.808: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.809: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.810: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.810: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.818: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.819: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.820: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.820: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.820: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.821: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.821: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.821: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.822: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.822: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.823: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.824: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.824: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.824: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.825: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.825: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.826: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.827: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.828: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.829: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.830: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.830: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.830: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.840: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.841: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.841: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.841: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.842: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.842: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.842: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.844: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.844: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.845: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.845: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.846: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.846: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.846: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.847: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.847: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.849: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.849: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.849: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.850: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.850: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.850: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.851: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.851: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.851: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.852: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.853: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.854: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.854: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.858: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.858: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.858: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.858: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.858: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.858: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.858: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:23.858: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.858: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.858: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.859: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.860: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.861: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.862: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.863: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.864: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.865: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 74
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.866: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.867: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.868: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.869: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.870: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.870: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.892: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.892: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.893: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:23.894: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.895: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.896: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 84
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.897: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.898: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.898: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.898: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.908: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.908: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.908: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.908: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.908: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:23.909: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.910: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.911: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.912: 69
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 87
(process:17837): libfprint-assembling-DEBUG: 04:24:23.913: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:23.914: 88
(process:17837): libfprint-assembling-DEBUG: 04:24:23.914: 86
(process:17837): libfprint-assembling-DEBUG: 04:24:23.914: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:23.923: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 76
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 74
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 48
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 64
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.924: 86
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 76
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:23.925: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.926: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 95
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 87
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:23.927: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.928: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:23.929: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.930: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.930: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.930: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.940: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.940: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.940: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.940: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.940: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.940: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 3
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 85
(process:17837): libfprint-assembling-DEBUG: 04:24:23.941: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 63
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 69
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 74
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:23.942: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 48
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 85
(process:17837): libfprint-assembling-DEBUG: 04:24:23.943: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 86
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 80
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 74
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 72
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:23.944: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 3
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.945: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:23.946: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:23.946: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.946: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.960: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:23.960: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:23.960: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.960: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.960: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.960: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.960: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.960: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.960: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:23.961: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 91
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 69
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.962: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 69
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 2
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:23.963: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 86
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 87
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.964: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 3
(process:17837): libfprint-assembling-DEBUG: 04:24:23.965: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.966: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 91
(process:17837): libfprint-assembling-DEBUG: 04:24:23.967: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 76
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 72
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:23.968: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 3
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 5
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 3
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.969: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:23.970: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.970: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:23.985: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:23.985: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:23.985: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.985: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:23.985: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.985: 88
(process:17837): libfprint-assembling-DEBUG: 04:24:23.985: 88
(process:17837): libfprint-assembling-DEBUG: 04:24:23.985: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 3
(process:17837): libfprint-assembling-DEBUG: 04:24:23.986: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 80
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 76
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 74
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.987: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 84
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 5
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 74
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 69
(process:17837): libfprint-assembling-DEBUG: 04:24:23.988: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 100
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:23.989: 95
(process:17837): libfprint-assembling-DEBUG: 04:24:23.990: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:23.990: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:23.990: 88
(process:17837): libfprint-assembling-DEBUG: 04:24:23.994: 86
(process:17837): libfprint-assembling-DEBUG: 04:24:23.994: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:23.994: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.994: 5
(process:17837): libfprint-assembling-DEBUG: 04:24:23.994: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.994: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:23.994: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:23.994: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.994: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 69
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:23.995: 63
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 84
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 95
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 84
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:23.996: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 63
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:23.997: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:23.998: 5
(process:17837): libfprint-assembling-DEBUG: 04:24:23.998: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:23.998: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:23.998: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:23.998: 5
(process:17837): libfprint-assembling-DEBUG: 04:24:24.006: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.006: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.006: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.006: 3
(process:17837): libfprint-assembling-DEBUG: 04:24:24.006: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.006: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:24.006: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:24.006: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:24.006: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.006: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 2
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 2
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 2
(process:17837): libfprint-assembling-DEBUG: 04:24:24.007: 1
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: offsets_filtered: 1694838264011104
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 5
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 5
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:24.011: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.012: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.013: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.014: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.015: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.016: 95
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 88
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 86
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 84
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.017: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.018: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.018: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.018: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.024: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.024: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:24.025: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.025: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.025: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.026: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.026: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.026: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.027: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.027: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.027: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.028: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.028: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.028: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.029: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.029: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.029: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.030: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.030: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.030: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.031: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.031: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.031: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.032: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.032: 99
(process:17837): libfprint-assembling-DEBUG: 04:24:24.032: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:24.033: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:24.033: 98
(process:17837): libfprint-assembling-DEBUG: 04:24:24.033: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:24.034: 97
(process:17837): libfprint-assembling-DEBUG: 04:24:24.042: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.043: 96
(process:17837): libfprint-assembling-DEBUG: 04:24:24.043: 95
(process:17837): libfprint-assembling-DEBUG: 04:24:24.043: 95
(process:17837): libfprint-assembling-DEBUG: 04:24:24.044: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:24.044: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:24.044: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:24.045: 93
(process:17837): libfprint-assembling-DEBUG: 04:24:24.045: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.045: 91
(process:17837): libfprint-assembling-DEBUG: 04:24:24.046: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:24.046: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:24.046: 88
(process:17837): libfprint-assembling-DEBUG: 04:24:24.047: 87
(process:17837): libfprint-assembling-DEBUG: 04:24:24.047: 87
(process:17837): libfprint-assembling-DEBUG: 04:24:24.047: 86
(process:17837): libfprint-assembling-DEBUG: 04:24:24.048: 85
(process:17837): libfprint-assembling-DEBUG: 04:24:24.048: 85
(process:17837): libfprint-assembling-DEBUG: 04:24:24.048: 84
(process:17837): libfprint-assembling-DEBUG: 04:24:24.048: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:24.048: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:24.048: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 79
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 75
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:24.049: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 69
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 64
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 64
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.050: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.051: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.052: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 48
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.053: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.054: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.054: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.054: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.059: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.060: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:24.060: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:24.061: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:24.061: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:24.061: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:24.062: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.062: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.062: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.063: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.063: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.063: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.064: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.064: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.064: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.064: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.065: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.065: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.065: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.066: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.066: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.066: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.067: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.067: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.068: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.068: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.068: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.069: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.069: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.069: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.070: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.070: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.070: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.070: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.070: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.070: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.070: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.070: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.070: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.071: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.072: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.073: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.074: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.074: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.074: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.074: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.083: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.084: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.084: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.084: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.085: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.085: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.085: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.086: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.086: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.086: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.087: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.087: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.087: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.088: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.088: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.088: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.089: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.089: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.089: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.090: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.091: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.092: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.093: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.094: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.094: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.094: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.099: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.100: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.100: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.100: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.101: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.101: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.101: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.102: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.102: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.102: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.103: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.103: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.103: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.104: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.104: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.104: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.105: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.105: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.105: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.105: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.112: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.112: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.113: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.114: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.115: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.116: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.117: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.118: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.118: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.118: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.120: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.121: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.122: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.123: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.124: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.125: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.126: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.126: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.126: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.130: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.130: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.130: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.130: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.130: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.130: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.130: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.131: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.132: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.133: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.134: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.134: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.138: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.138: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.138: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.138: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.138: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.138: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.138: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.138: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.139: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.140: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 30
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.141: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.142: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.142: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.142: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.146: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.146: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.146: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.146: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.146: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.146: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.146: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.146: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.147: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.148: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.149: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.150: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.150: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.152: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.153: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.154: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.155: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.156: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.157: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.158: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.158: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.158: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.162: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.162: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.162: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.162: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.162: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.162: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.162: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.163: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.164: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.165: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.166: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.166: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.166: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.170: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.170: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.170: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.170: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.170: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.170: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.170: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.170: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.171: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.172: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.173: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.174: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.174: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.174: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.178: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.178: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.178: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.178: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.178: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.178: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.178: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 19
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.179: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.180: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.181: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 18
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.182: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.183: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.184: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 16
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.185: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.186: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.186: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.186: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.194: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.194: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.194: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.194: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.194: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.194: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.194: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.195: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.196: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.197: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.198: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.199: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.200: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.201: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.202: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.202: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.202: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.206: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.206: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.206: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.206: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.206: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.206: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.206: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.206: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.207: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 11
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.208: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 12
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:24.209: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.210: 69
(process:17837): libfprint-assembling-DEBUG: 04:24:24.210: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:24.214: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:24.214: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:24.214: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:24.214: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:24.214: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.214: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.214: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.214: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:24.215: 64
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 64
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 48
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.216: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.217: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.218: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.218: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.218: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.218: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.218: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.218: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.218: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:24.218: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:24.218: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:24.218: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 94
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 92
(process:17837): libfprint-assembling-DEBUG: 04:24:24.219: 90
(process:17837): libfprint-assembling-DEBUG: 04:24:24.220: 89
(process:17837): libfprint-assembling-DEBUG: 04:24:24.220: 87
(process:17837): libfprint-assembling-DEBUG: 04:24:24.220: 83
(process:17837): libfprint-assembling-DEBUG: 04:24:24.220: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:24.220: 81
(process:17837): libfprint-assembling-DEBUG: 04:24:24.220: 77
(process:17837): libfprint-assembling-DEBUG: 04:24:24.220: 70
(process:17837): libfprint-assembling-DEBUG: 04:24:24.220: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.220: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.226: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.226: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:24.226: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.226: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:24.226: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:24.226: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.226: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.227: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 20
(process:17837): libfprint-assembling-DEBUG: 04:24:24.228: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 24
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.229: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:24.230: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:24.231: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 60
(process:17837): libfprint-assembling-DEBUG: 04:24:24.232: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 54
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.233: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.234: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.234: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.234: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.238: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.238: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:24.238: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.238: 43
(process:17837): libfprint-assembling-DEBUG: 04:24:24.238: 42
(process:17837): libfprint-assembling-DEBUG: 04:24:24.238: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.238: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.239: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 36
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.240: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 47
(process:17837): libfprint-assembling-DEBUG: 04:24:24.241: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.242: 46
(process:17837): libfprint-assembling-DEBUG: 04:24:24.242: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.242: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.245: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.245: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.245: 32
(process:17837): libfprint-assembling-DEBUG: 04:24:24.245: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.245: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 26
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.246: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 23
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 25
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.247: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.248: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.249: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 62
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:24.250: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:24.251: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.251: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:24.251: 56
(process:17837): libfprint-assembling-DEBUG: 04:24:24.251: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.251: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.260: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.260: 49
(process:17837): libfprint-assembling-DEBUG: 04:24:24.260: 44
(process:17837): libfprint-assembling-DEBUG: 04:24:24.260: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.260: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.260: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.260: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.260: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.261: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 37
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 38
(process:17837): libfprint-assembling-DEBUG: 04:24:24.262: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.263: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 52
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 73
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 71
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 69
(process:17837): libfprint-assembling-DEBUG: 04:24:24.264: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 68
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 67
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.265: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:24.266: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:24.266: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.266: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:24.268: 66
(process:17837): libfprint-assembling-DEBUG: 04:24:24.268: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.268: 61
(process:17837): libfprint-assembling-DEBUG: 04:24:24.269: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.269: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.270: 59
(process:17837): libfprint-assembling-DEBUG: 04:24:24.270: 57
(process:17837): libfprint-assembling-DEBUG: 04:24:24.270: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.271: 51
(process:17837): libfprint-assembling-DEBUG: 04:24:24.271: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.272: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.272: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.272: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.273: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.273: 33
(process:17837): libfprint-assembling-DEBUG: 04:24:24.274: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.274: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.274: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.275: 34
(process:17837): libfprint-assembling-DEBUG: 04:24:24.275: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.276: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.276: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.276: 63
(process:17837): libfprint-assembling-DEBUG: 04:24:24.277: 63
(process:17837): libfprint-assembling-DEBUG: 04:24:24.277: 63
(process:17837): libfprint-assembling-DEBUG: 04:24:24.277: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.282: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.282: 63
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 65
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 63
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:24.283: 58
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 55
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 50
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 53
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 45
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 41
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 40
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 39
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 35
(process:17837): libfprint-assembling-DEBUG: 04:24:24.284: 31
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 29
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 28
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 27
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 22
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 21
(process:17837): libfprint-assembling-DEBUG: 04:24:24.285: 17
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 15
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 14
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 13
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 10
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 9
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 8
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:24.286: 7
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.287: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.288: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.288: 4
(process:17837): libfprint-assembling-DEBUG: 04:24:24.288: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.288: 6
(process:17837): libfprint-assembling-DEBUG: 04:24:24.288: 1
(process:17837): libfprint-image_device-DEBUG: 04:24:24.301: Image device captured an image
(process:17837): libfprint-image_device-DEBUG: 04:24:24.302: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17837): libfprint-device-DEBUG: 04:24:24.302: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17837): libfprint-device-DEBUG: 04:24:24.303: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17837): libfprint-image_device-DEBUG: 04:24:24.303: Image device reported finger status: off
(process:17837): libfprint-image_device-DEBUG: 04:24:24.303: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17837): libfprint-image_device-DEBUG: 04:24:24.304: Deactivating image device
(process:17837): libfprint-image_device-DEBUG: 04:24:24.304: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17837): libfprint-SSM-DEBUG: 04:24:24.306: [vfs0050] SSM_STATES entering state 10
(process:17837): libfprint-SSM-DEBUG: 04:24:24.306: [vfs0050] SSM_STATES entering state 3
(process:17837): libfprint-SSM-DEBUG: 04:24:24.306: [vfs0050] SUBSM1_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:24.389: [vfs0050] SUBSM1_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:24.426: [vfs0050] SUBSM1_STATES entering state 2
(process:17837): libfprint-SSM-DEBUG: 04:24:24.453: [vfs0050] SUBSM1_STATES completed successfully
(process:17837): libfprint-SSM-DEBUG: 04:24:24.453: [vfs0050] SSM_STATES entering state 4
(process:17837): libfprint-SSM-DEBUG: 04:24:24.454: [vfs0050] SUBSM2_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:24.502: [vfs0050] SUBSM2_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:24.554: [vfs0050] SUBSM2_STATES entering state 2
(process:17837): libfprint-image-DEBUG: 04:24:24.557: Minutiae scan completed in 0.234925 secs
(process:17837): libfprint-SSM-DEBUG: 04:24:24.590: [vfs0050] SUBSM2_STATES entering state 3
(process:17837): libfprint-SSM-DEBUG: 04:24:24.618: [vfs0050] SUBSM2_STATES entering state 4
(process:17837): libfprint-SSM-DEBUG: 04:24:24.648: [vfs0050] SUBSM2_STATES entering state 5
(process:17837): libfprint-SSM-DEBUG: 04:24:24.672: [vfs0050] SUBSM2_STATES entering state 6
(process:17837): libfprint-SSM-DEBUG: 04:24:24.672: [vfs0050] SUBSM1_STATES entering state 0
(process:17837): libfprint-SSM-DEBUG: 04:24:24.702: [vfs0050] SUBSM1_STATES entering state 1
(process:17837): libfprint-SSM-DEBUG: 04:24:24.738: [vfs0050] SUBSM1_STATES entering state 2
(process:17837): libfprint-SSM-DEBUG: 04:24:24.766: [vfs0050] SUBSM1_STATES completed successfully
(process:17837): libfprint-SSM-DEBUG: 04:24:24.766: [vfs0050] SUBSM2_STATES completed successfully
(process:17837): libfprint-SSM-DEBUG: 04:24:24.766: [vfs0050] SSM_STATES entering state 5
(process:17837): libfprint-SSM-DEBUG: 04:24:24.766: [vfs0050] SSM_STATES completed successfully
(process:17837): libfprint-image_device-DEBUG: 04:24:24.766: Image device deactivation completed
(process:17837): libfprint-image_device-DEBUG: 04:24:24.766: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17837): libfprint-device-DEBUG: 04:24:24.767: Device reported capture completion
(process:17837): libfprint-device-DEBUG: 04:24:24.767: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17837): libfprint-device-DEBUG: 04:24:24.767: Updated temperature model after 2.34 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17837): libfprint-image_device-DEBUG: 04:24:24.780: Image device close completed
(process:17837): libfprint-device-DEBUG: 04:24:24.780: Device reported close completion
(process:17837): libfprint-device-DEBUG: 04:24:24.789: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17837): libfprint-device-DEBUG: 04:24:24.789: Updated temperature model after 0.02 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17834): DEBUG: 04:24:25.698: umockdev.vala:150: Removing test bed /tmp/umockdev.BCABB2
(umockdev-run:17834): GLib-DEBUG: 04:24:25.751: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-ev6i0qog/capture.png and /<<PKGBUILDDIR>>/tests/vfs0050/capture.png
==============================================================================
================================== 102/116 ===================================
test: libfprint:drivers / vfs301
start time: 04:24:23
duration: 4.91s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 FP_DRIVERS_WHITELIST=vfs301 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=129 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/vfs301
----------------------------------- stdout -----------------------------------
** (umockdev-run:17849): DEBUG: 04:24:23.672: umockdev.vala:123: Created udev test bed /tmp/umockdev.RYEQB2
** (umockdev-run:17849): DEBUG: 04:24:23.673: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3
** (umockdev-run:17849): DEBUG: 04:24:23.698: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 (subsystem usb)
** (umockdev-run:17849): DEBUG: 04:24:23.743: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.RYEQB2/dev/bus/usb/002/005
** (umockdev-run:17849): DEBUG: 04:24:23.744: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1
** (umockdev-run:17849): DEBUG: 04:24:23.763: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1 (subsystem usb)
** (umockdev-run:17849): DEBUG: 04:24:23.807: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.RYEQB2/dev/bus/usb/002/002
** (umockdev-run:17849): DEBUG: 04:24:23.807: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2
** (umockdev-run:17849): DEBUG: 04:24:23.817: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0/usb2 (subsystem usb)
** (umockdev-run:17849): DEBUG: 04:24:23.856: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.RYEQB2/dev/bus/usb/002/001
** (umockdev-run:17849): DEBUG: 04:24:23.857: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0
** (umockdev-run:17849): DEBUG: 04:24:23.866: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0 (subsystem pci)
(umockdev-run:17849): GLib-GIO-DEBUG: 04:24:23.900: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
(umockdev-run:17849): GLib-DEBUG: 04:24:24.018: pidfd_open(17852) failed with error: Function not implemented
(process:17852): libfprint-context-DEBUG: 04:24:24.435: Initializing FpContext (libfprint version 1.94.6)
(process:17852): libfprint-context-DEBUG: 04:24:24.482: No driver found for USB device 8087:0020
(process:17852): libfprint-context-DEBUG: 04:24:24.483: No driver found for USB device 1D6B:0002
(process:17852): libfprint-device-DEBUG: 04:24:24.494: Device reported probe completion
(process:17852): libfprint-device-DEBUG: 04:24:24.499: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17852): libfprint-device-DEBUG: 04:24:24.499: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17852): libfprint-image_device-DEBUG: 04:24:24.538: Image device open completed
(process:17852): libfprint-device-DEBUG: 04:24:24.538: Device reported open completion
(process:17852): libfprint-device-DEBUG: 04:24:24.538: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17852): libfprint-device-DEBUG: 04:24:24.539: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17852): libfprint-device-DEBUG: 04:24:24.540: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17852): libfprint-image_device-DEBUG: 04:24:24.541: Activating image device
(process:17852): libfprint-image_device-DEBUG: 04:24:24.541: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17852): libfprint-SSM-DEBUG: 04:24:24.541: [vfs301] 1 entering state 0
(process:17852): libfprint-device-DEBUG: 04:24:24.647: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17852): libfprint-SSM-DEBUG: 04:24:26.771: [vfs301] 1 completed successfully
(process:17852): libfprint-image_device-DEBUG: 04:24:26.771: Image device activation completed
(process:17852): libfprint-image_device-DEBUG: 04:24:26.771: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17852): libfprint-image_device-DEBUG: 04:24:26.771: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17852): libfprint-SSM-DEBUG: 04:24:26.772: [vfs301] M_LOOP_NUM_STATES entering state 0
(process:17852): libfprint-SSM-DEBUG: 04:24:26.809: [vfs301] M_LOOP_NUM_STATES entering state 1
(process:17852): libfprint-device-DEBUG: 04:24:26.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17852): libfprint-SSM-DEBUG: 04:24:27.010: [vfs301] M_LOOP_NUM_STATES entering state 2
(process:17852): libfprint-SSM-DEBUG: 04:24:27.057: [vfs301] M_LOOP_NUM_STATES entering state 1
(process:17852): libfprint-SSM-DEBUG: 04:24:27.262: [vfs301] M_LOOP_NUM_STATES entering state 2
(process:17852): libfprint-SSM-DEBUG: 04:24:27.314: [vfs301] M_LOOP_NUM_STATES entering state 3
(process:17852): libfprint-device-DEBUG: 04:24:27.314: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17852): libfprint-image_device-DEBUG: 04:24:27.314: Image device reported finger status: on
(process:17852): libfprint-image_device-DEBUG: 04:24:27.314: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17852): libfprint-SSM-DEBUG: 04:24:27.359: [vfs301] M_LOOP_NUM_STATES entering state 4
(process:17852): libfprint-SSM-DEBUG: 04:24:27.542: [vfs301] M_LOOP_NUM_STATES entering state 5
(process:17852): libfprint-SSM-DEBUG: 04:24:27.702: [vfs301] M_LOOP_NUM_STATES entering state 6
(process:17852): libfprint-image_device-DEBUG: 04:24:27.703: Image device captured an image
(process:17852): libfprint-image_device-DEBUG: 04:24:27.704: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17852): libfprint-device-DEBUG: 04:24:27.704: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17852): libfprint-SSM-DEBUG: 04:24:27.704: [vfs301] M_LOOP_NUM_STATES completed successfully
(process:17852): libfprint-device-DEBUG: 04:24:27.704: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17852): libfprint-image_device-DEBUG: 04:24:27.704: Image device reported finger status: off
(process:17852): libfprint-image_device-DEBUG: 04:24:27.704: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17852): libfprint-image_device-DEBUG: 04:24:27.705: Deactivating image device
(process:17852): libfprint-image_device-DEBUG: 04:24:27.705: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17852): libfprint-image_device-DEBUG: 04:24:27.705: Image device deactivation completed
(process:17852): libfprint-image_device-DEBUG: 04:24:27.705: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17852): libfprint-image-DEBUG: 04:24:27.823: Minutiae scan completed in 0.116640 secs
(process:17852): libfprint-device-DEBUG: 04:24:27.830: Device reported capture completion
(process:17852): libfprint-device-DEBUG: 04:24:27.831: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17852): libfprint-device-DEBUG: 04:24:27.831: Updated temperature model after 3.18 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17852): libfprint-image_device-DEBUG: 04:24:27.836: Image device close completed
(process:17852): libfprint-device-DEBUG: 04:24:27.836: Device reported close completion
(process:17852): libfprint-device-DEBUG: 04:24:27.840: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17852): libfprint-device-DEBUG: 04:24:27.840: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17849): DEBUG: 04:24:28.214: umockdev.vala:150: Removing test bed /tmp/umockdev.RYEQB2
(umockdev-run:17849): GLib-DEBUG: 04:24:28.274: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-50thwznk/capture.png and /<<PKGBUILDDIR>>/tests/vfs301/capture.png
==============================================================================
================================== 103/116 ===================================
test: libfprint:drivers / vfs5011
start time: 04:24:26
duration: 5.98s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=161 NO_AT_BRIDGE=1 FP_DRIVERS_WHITELIST=vfs5011 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/vfs5011
----------------------------------- stdout -----------------------------------
** (umockdev-run:17860): DEBUG: 04:24:26.274: umockdev.vala:123: Created udev test bed /tmp/umockdev.RTYEB2
** (umockdev-run:17860): DEBUG: 04:24:26.275: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2/2-6
** (umockdev-run:17860): DEBUG: 04:24:26.295: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb2/2-6 (subsystem usb)
** (umockdev-run:17860): DEBUG: 04:24:26.332: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.RTYEB2/dev/bus/usb/002/017
** (umockdev-run:17860): DEBUG: 04:24:26.333: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2
** (umockdev-run:17860): DEBUG: 04:24:26.352: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb2 (subsystem usb)
** (umockdev-run:17860): DEBUG: 04:24:26.387: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.RTYEB2/dev/bus/usb/002/001
** (umockdev-run:17860): DEBUG: 04:24:26.388: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17860): DEBUG: 04:24:26.393: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17860): GLib-GIO-DEBUG: 04:24:26.430: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
(umockdev-run:17860): GLib-DEBUG: 04:24:26.510: pidfd_open(17863) failed with error: Function not implemented
(process:17863): libfprint-context-DEBUG: 04:24:26.772: Initializing FpContext (libfprint version 1.94.6)
(process:17863): libfprint-context-DEBUG: 04:24:26.789: No driver found for USB device 1D6B:0002
(process:17863): libfprint-device-DEBUG: 04:24:26.791: Device reported probe completion
(process:17863): libfprint-device-DEBUG: 04:24:26.792: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17863): libfprint-device-DEBUG: 04:24:26.793: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17863): libfprint-SSM-DEBUG: 04:24:26.858: [vfs5011] DEV_OPEN_NUM_STATES entering state 0
(process:17863): libfprint-SSM-DEBUG: 04:24:26.859: [vfs5011] DEVICE OPEN entering state 0
(process:17863): libfprint-vfs5011-DEBUG: 04:24:26.860: Sending vfs5011_cmd_01
(process:17863): libfprint-SSM-DEBUG: 04:24:26.889: [vfs5011] DEVICE OPEN entering state 1
(process:17863): libfprint-vfs5011-DEBUG: 04:24:26.890: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:26.928: Got 38 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:26.928: [vfs5011] DEVICE OPEN entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:26.928: Sending vfs5011_cmd_19
(process:17863): libfprint-SSM-DEBUG: 04:24:26.954: [vfs5011] DEVICE OPEN entering state 3
(process:17863): libfprint-vfs5011-DEBUG: 04:24:26.954: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:26.985: Got 64 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:26.985: [vfs5011] DEVICE OPEN entering state 4
(process:17863): libfprint-vfs5011-DEBUG: 04:24:26.985: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.018: Got 4 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:27.018: [vfs5011] DEVICE OPEN entering state 5
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.018: Sending vfs5011_init_00
(process:17863): libfprint-SSM-DEBUG: 04:24:27.045: [vfs5011] DEVICE OPEN entering state 6
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.045: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.078: Got 6 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:27.078: [vfs5011] DEVICE OPEN entering state 7
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.078: Sending vfs5011_init_01
(process:17863): libfprint-SSM-DEBUG: 04:24:27.105: [vfs5011] DEVICE OPEN entering state 8
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.105: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.143: Got 7 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:27.143: [vfs5011] DEVICE OPEN entering state 9
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.143: Sending vfs5011_init_02
(process:17863): libfprint-SSM-DEBUG: 04:24:27.173: [vfs5011] DEVICE OPEN entering state 10
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.174: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:27.204: [vfs5011] DEVICE OPEN entering state 11
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.205: Sending vfs5011_cmd_01
(process:17863): libfprint-SSM-DEBUG: 04:24:27.231: [vfs5011] DEVICE OPEN entering state 12
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.232: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.260: Got 38 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:27.260: [vfs5011] DEVICE OPEN entering state 13
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.260: Sending vfs5011_cmd_1A
(process:17863): libfprint-SSM-DEBUG: 04:24:27.291: [vfs5011] DEVICE OPEN entering state 14
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.291: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:27.318: [vfs5011] DEVICE OPEN entering state 15
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.318: Sending vfs5011_init_03
(process:17863): libfprint-SSM-DEBUG: 04:24:27.345: [vfs5011] DEVICE OPEN entering state 16
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.345: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:27.376: [vfs5011] DEVICE OPEN entering state 17
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.376: Sending vfs5011_init_04
(process:17863): libfprint-SSM-DEBUG: 04:24:27.407: [vfs5011] DEVICE OPEN entering state 18
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.407: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:27.434: [vfs5011] DEVICE OPEN entering state 19
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.434: Receiving 256 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.471: Got 256 bytes out of 256
(process:17863): libfprint-SSM-DEBUG: 04:24:27.471: [vfs5011] DEVICE OPEN entering state 20
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.472: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.501: Got 32 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:27.501: [vfs5011] DEVICE OPEN entering state 21
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.501: Sending vfs5011_cmd_1A
(process:17863): libfprint-SSM-DEBUG: 04:24:27.528: [vfs5011] DEVICE OPEN entering state 22
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.528: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:27.565: [vfs5011] DEVICE OPEN entering state 23
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.565: Sending vfs5011_init_05
(process:17863): libfprint-SSM-DEBUG: 04:24:27.592: [vfs5011] DEVICE OPEN entering state 24
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.592: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:27.619: [vfs5011] DEVICE OPEN entering state 25
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.619: Sending vfs5011_cmd_01
(process:17863): libfprint-SSM-DEBUG: 04:24:27.646: [vfs5011] DEVICE OPEN entering state 26
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.650: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.679: Got 38 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:27.679: [vfs5011] DEVICE OPEN entering state 27
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.679: Sending vfs5011_init_06
(process:17863): libfprint-SSM-DEBUG: 04:24:27.714: [vfs5011] DEVICE OPEN entering state 28
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.714: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:27.737: [vfs5011] DEVICE OPEN entering state 29
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.737: Receiving 17216 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.775: Got 17216 bytes out of 17216
(process:17863): libfprint-SSM-DEBUG: 04:24:27.775: [vfs5011] DEVICE OPEN entering state 30
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.775: Receiving 32 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.808: Got 32 bytes out of 32
(process:17863): libfprint-SSM-DEBUG: 04:24:27.808: [vfs5011] DEVICE OPEN entering state 31
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.808: Sending vfs5011_init_07
(process:17863): libfprint-SSM-DEBUG: 04:24:27.844: [vfs5011] DEVICE OPEN entering state 32
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.844: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:27.877: [vfs5011] DEVICE OPEN entering state 33
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.877: Receiving 45056 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.909: Got 45056 bytes out of 45056
(process:17863): libfprint-SSM-DEBUG: 04:24:27.909: [vfs5011] DEVICE OPEN entering state 34
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.909: Sending vfs5011_init_08
(process:17863): libfprint-SSM-DEBUG: 04:24:27.940: [vfs5011] DEVICE OPEN entering state 35
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.940: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:27.977: [vfs5011] DEVICE OPEN entering state 36
(process:17863): libfprint-vfs5011-DEBUG: 04:24:27.977: Receiving 16896 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.006: Got 16896 bytes out of 16896
(process:17863): libfprint-SSM-DEBUG: 04:24:28.006: [vfs5011] DEVICE OPEN entering state 37
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.006: Sending vfs5011_init_09
(process:17863): libfprint-SSM-DEBUG: 04:24:28.037: [vfs5011] DEVICE OPEN entering state 38
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.037: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:28.062: [vfs5011] DEVICE OPEN entering state 39
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.070: Receiving 4928 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.099: Got 4928 bytes out of 4928
(process:17863): libfprint-SSM-DEBUG: 04:24:28.099: [vfs5011] DEVICE OPEN entering state 40
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.099: Sending vfs5011_init_10
(process:17863): libfprint-SSM-DEBUG: 04:24:28.121: [vfs5011] DEVICE OPEN entering state 41
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.121: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:28.154: [vfs5011] DEVICE OPEN entering state 42
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.154: Receiving 5632 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.191: Got 5632 bytes out of 5632
(process:17863): libfprint-SSM-DEBUG: 04:24:28.192: [vfs5011] DEVICE OPEN entering state 43
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.192: Sending vfs5011_init_11
(process:17863): libfprint-SSM-DEBUG: 04:24:28.220: [vfs5011] DEVICE OPEN entering state 44
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.220: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:28.249: [vfs5011] DEVICE OPEN entering state 45
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.249: Receiving 5632 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.286: Got 5632 bytes out of 5632
(process:17863): libfprint-SSM-DEBUG: 04:24:28.286: [vfs5011] DEVICE OPEN entering state 46
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.286: Sending vfs5011_init_12
(process:17863): libfprint-SSM-DEBUG: 04:24:28.313: [vfs5011] DEVICE OPEN entering state 47
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.313: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:28.341: [vfs5011] DEVICE OPEN entering state 48
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.341: Receiving 3328 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.369: Got 3328 bytes out of 3328
(process:17863): libfprint-SSM-DEBUG: 04:24:28.369: [vfs5011] DEVICE OPEN entering state 49
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.369: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.402: Got 32 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:28.402: [vfs5011] DEVICE OPEN entering state 50
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.402: Sending vfs5011_init_13
(process:17863): libfprint-SSM-DEBUG: 04:24:28.434: [vfs5011] DEVICE OPEN entering state 51
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.434: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:28.467: [vfs5011] DEVICE OPEN entering state 52
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.467: Sending vfs5011_cmd_1A
(process:17863): libfprint-SSM-DEBUG: 04:24:28.510: [vfs5011] DEVICE OPEN entering state 53
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.510: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:28.546: [vfs5011] DEVICE OPEN entering state 54
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.546: Sending vfs5011_init_03
(process:17863): libfprint-SSM-DEBUG: 04:24:28.578: [vfs5011] DEVICE OPEN entering state 55
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.578: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:28.615: [vfs5011] DEVICE OPEN entering state 56
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.615: Sending vfs5011_init_14
(process:17863): libfprint-SSM-DEBUG: 04:24:28.654: [vfs5011] DEVICE OPEN entering state 57
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.654: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:28.692: [vfs5011] DEVICE OPEN entering state 58
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.692: Receiving 4800 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.735: Got 4800 bytes out of 4800
(process:17863): libfprint-SSM-DEBUG: 04:24:28.735: [vfs5011] DEVICE OPEN entering state 59
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.735: Sending vfs5011_cmd_1A
(process:17863): libfprint-SSM-DEBUG: 04:24:28.773: [vfs5011] DEVICE OPEN entering state 60
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.773: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:28.815: [vfs5011] DEVICE OPEN entering state 61
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.815: Sending vfs5011_init_02
(process:17863): libfprint-SSM-DEBUG: 04:24:28.866: [vfs5011] DEVICE OPEN entering state 62
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.866: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:28.912: [vfs5011] DEVICE OPEN entering state 63
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.912: Sending vfs5011_cmd_27
(process:17863): libfprint-SSM-DEBUG: 04:24:28.947: [vfs5011] DEVICE OPEN entering state 64
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.948: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.987: Got 22 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:28.988: [vfs5011] DEVICE OPEN entering state 65
(process:17863): libfprint-vfs5011-DEBUG: 04:24:28.988: Sending vfs5011_cmd_1A
(process:17863): libfprint-SSM-DEBUG: 04:24:29.025: [vfs5011] DEVICE OPEN entering state 66
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.025: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:29.062: [vfs5011] DEVICE OPEN entering state 67
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.062: Sending vfs5011_init_15
(process:17863): libfprint-SSM-DEBUG: 04:24:29.099: [vfs5011] DEVICE OPEN entering state 68
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.099: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:29.138: [vfs5011] DEVICE OPEN entering state 69
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.138: Sending vfs5011_init_16
(process:17863): libfprint-SSM-DEBUG: 04:24:29.174: [vfs5011] DEVICE OPEN entering state 70
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.174: Receiving 2368 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.231: Got 2368 bytes out of 2368
(process:17863): libfprint-SSM-DEBUG: 04:24:29.232: [vfs5011] DEVICE OPEN entering state 71
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.232: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.272: Got 36 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:29.272: [vfs5011] DEVICE OPEN entering state 72
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.273: Receiving 4800 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.309: Got 4800 bytes out of 4800
(process:17863): libfprint-SSM-DEBUG: 04:24:29.309: [vfs5011] DEVICE OPEN entering state 73
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.309: Sending vfs5011_init_17
(process:17863): libfprint-SSM-DEBUG: 04:24:29.358: [vfs5011] DEVICE OPEN entering state 74
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.358: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:29.399: [vfs5011] DEVICE OPEN entering state 75
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.400: Sending vfs5011_init_18
(process:17863): libfprint-SSM-DEBUG: 04:24:29.438: [vfs5011] DEVICE OPEN entering state 76
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.438: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:29.475: [vfs5011] DEVICE OPEN completed successfully
(process:17863): libfprint-SSM-DEBUG: 04:24:29.475: [vfs5011] DEV_OPEN_NUM_STATES completed successfully
(process:17863): libfprint-image_device-DEBUG: 04:24:29.475: Image device open completed
(process:17863): libfprint-device-DEBUG: 04:24:29.476: Device reported open completion
(process:17863): libfprint-device-DEBUG: 04:24:29.476: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17863): libfprint-device-DEBUG: 04:24:29.476: Updated temperature model after 2.68 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17863): libfprint-device-DEBUG: 04:24:29.478: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17863): libfprint-image_device-DEBUG: 04:24:29.478: Activating image device
(process:17863): libfprint-image_device-DEBUG: 04:24:29.478: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.478: device initialized
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.478: creating ssm
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.479: starting ssm
(process:17863): libfprint-SSM-DEBUG: 04:24:29.479: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 0
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.479: main_loop: state 0
(process:17863): libfprint-SSM-DEBUG: 04:24:29.479: [vfs5011] ACTIVATE REQUEST entering state 0
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.479: Sending vfs5011_cmd_04
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.497: ssm done, getting out
(process:17863): libfprint-SSM-DEBUG: 04:24:29.516: [vfs5011] ACTIVATE REQUEST entering state 1
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.517: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.559: Got 64 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:29.559: [vfs5011] ACTIVATE REQUEST entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.559: Receiving 84032 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.601: Got 176 bytes out of 84032
(process:17863): libfprint-SSM-DEBUG: 04:24:29.601: [vfs5011] ACTIVATE REQUEST entering state 3
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.601: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:29.644: [vfs5011] ACTIVATE REQUEST entering state 4
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.644: Sending vfs5011_cmd_1A
(process:17863): libfprint-SSM-DEBUG: 04:24:29.681: [vfs5011] ACTIVATE REQUEST entering state 5
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.681: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:29.719: [vfs5011] ACTIVATE REQUEST entering state 6
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.719: Sending vfs5011_prepare_00
(process:17863): libfprint-SSM-DEBUG: 04:24:29.759: [vfs5011] ACTIVATE REQUEST entering state 7
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.759: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:29.785: [vfs5011] ACTIVATE REQUEST entering state 8
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.785: Sending vfs5011_cmd_1A
(process:17863): libfprint-SSM-DEBUG: 04:24:29.819: [vfs5011] ACTIVATE REQUEST entering state 9
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.819: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:29.845: [vfs5011] ACTIVATE REQUEST entering state 10
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.845: Sending vfs5011_prepare_01
(process:17863): libfprint-SSM-DEBUG: 04:24:29.871: [vfs5011] ACTIVATE REQUEST entering state 11
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.871: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:29.901: [vfs5011] ACTIVATE REQUEST entering state 12
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.902: Sending vfs5011_prepare_02
(process:17863): libfprint-device-DEBUG: 04:24:29.919: Updated temperature model after 0.44 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17863): libfprint-SSM-DEBUG: 04:24:29.928: [vfs5011] ACTIVATE REQUEST entering state 13
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.928: Receiving 2368 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.961: Got 2368 bytes out of 2368
(process:17863): libfprint-SSM-DEBUG: 04:24:29.961: [vfs5011] ACTIVATE REQUEST entering state 14
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.961: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.998: Got 36 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:29.998: [vfs5011] ACTIVATE REQUEST entering state 15
(process:17863): libfprint-vfs5011-DEBUG: 04:24:29.998: Receiving 4800 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.027: Got 4800 bytes out of 4800
(process:17863): libfprint-SSM-DEBUG: 04:24:30.027: [vfs5011] ACTIVATE REQUEST entering state 16
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.027: Sending vfs5011_prepare_03
(process:17863): libfprint-SSM-DEBUG: 04:24:30.060: [vfs5011] ACTIVATE REQUEST entering state 17
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.060: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.085: [vfs5011] ACTIVATE REQUEST entering state 18
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.085: Sending vfs5011_prepare_04
(process:17863): libfprint-SSM-DEBUG: 04:24:30.117: [vfs5011] ACTIVATE REQUEST entering state 19
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.117: Receiving 2368 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.148: [vfs5011] ACTIVATE REQUEST completed successfully
(process:17863): libfprint-SSM-DEBUG: 04:24:30.148: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 1
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.148: main_loop: state 1
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.148: capture_init
(process:17863): libfprint-image_device-DEBUG: 04:24:30.148: Image device activation completed
(process:17863): libfprint-image_device-DEBUG: 04:24:30.148: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17863): libfprint-image_device-DEBUG: 04:24:30.149: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17863): libfprint-device-DEBUG: 04:24:30.149: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17863): libfprint-SSM-DEBUG: 04:24:30.149: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.149: main_loop: state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.149: capture_chunk_async: capture 256 lines, already have 0
(process:17863): libfprint-device-DEBUG: 04:24:30.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17863): libfprint-image_device-DEBUG: 04:24:30.179: Image device reported finger status: on
(process:17863): libfprint-image_device-DEBUG: 04:24:30.179: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.179: process_chunk: got 61440 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.179: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.180: main_loop: state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.180: capture_chunk_async: capture 256 lines, already have 6
(process:17863): libfprint-image_device-DEBUG: 04:24:30.217: Image device reported finger status: on
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.217: process_chunk: got 61440 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.218: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.218: main_loop: state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.218: capture_chunk_async: capture 256 lines, already have 25
(process:17863): libfprint-image_device-DEBUG: 04:24:30.247: Image device reported finger status: on
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.247: process_chunk: got 61440 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.248: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.248: main_loop: state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.248: capture_chunk_async: capture 256 lines, already have 54
(process:17863): libfprint-image_device-DEBUG: 04:24:30.277: Image device reported finger status: on
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.278: process_chunk: got 61440 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.282: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.282: main_loop: state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.282: capture_chunk_async: capture 256 lines, already have 89
(process:17863): libfprint-image_device-DEBUG: 04:24:30.432: Image device reported finger status: on
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.432: process_chunk: got 61440 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.433: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.433: main_loop: state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.433: capture_chunk_async: capture 256 lines, already have 117
(process:17863): libfprint-image_device-DEBUG: 04:24:30.463: Image device reported finger status: on
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.463: process_chunk: got 61440 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.463: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.463: main_loop: state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.463: capture_chunk_async: capture 256 lines, already have 144
(process:17863): libfprint-image_device-DEBUG: 04:24:30.493: Image device reported finger status: on
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.493: process_chunk: got 61440 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.494: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.494: main_loop: state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.498: capture_chunk_async: capture 256 lines, already have 180
(process:17863): libfprint-image_device-DEBUG: 04:24:30.527: Image device reported finger status: on
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.527: process_chunk: got 61440 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.528: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.528: main_loop: state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.528: capture_chunk_async: capture 256 lines, already have 273
(process:17863): libfprint-image_device-DEBUG: 04:24:30.562: Image device reported finger status: on
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.562: process_chunk: got 61440 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.562: process_chunk: got 50 empty lines, finishing
(process:17863): libfprint-SSM-DEBUG: 04:24:30.562: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 3
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.562: main_loop: state 3
(process:17863): libfprint-SSM-DEBUG: 04:24:30.563: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 4
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.563: main_loop: state 4
(process:17863): libfprint-SSM-DEBUG: 04:24:30.563: [vfs5011] PREPARE CAPTURE entering state 0
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.563: Sending vfs5011_cmd_04
(process:17863): libfprint-SSM-DEBUG: 04:24:30.594: [vfs5011] PREPARE CAPTURE entering state 1
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.594: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.623: Got 64 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:30.623: [vfs5011] PREPARE CAPTURE entering state 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.623: Receiving 84032 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.656: Got 176 bytes out of 84032
(process:17863): libfprint-SSM-DEBUG: 04:24:30.657: [vfs5011] PREPARE CAPTURE entering state 3
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.657: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.690: [vfs5011] PREPARE CAPTURE entering state 4
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.690: Sending vfs5011_cmd_1A
(process:17863): libfprint-SSM-DEBUG: 04:24:30.717: [vfs5011] PREPARE CAPTURE entering state 5
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.717: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.744: [vfs5011] PREPARE CAPTURE entering state 6
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.744: Sending vfs5011_prepare_00
(process:17863): libfprint-SSM-DEBUG: 04:24:30.775: [vfs5011] PREPARE CAPTURE entering state 7
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.775: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.802: [vfs5011] PREPARE CAPTURE entering state 8
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.802: Sending vfs5011_cmd_1A
(process:17863): libfprint-SSM-DEBUG: 04:24:30.829: [vfs5011] PREPARE CAPTURE entering state 9
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.829: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.860: [vfs5011] PREPARE CAPTURE entering state 10
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.860: Sending vfs5011_prepare_01
(process:17863): libfprint-SSM-DEBUG: 04:24:30.891: [vfs5011] PREPARE CAPTURE entering state 11
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.891: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:30.922: [vfs5011] PREPARE CAPTURE entering state 12
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.922: Sending vfs5011_prepare_02
(process:17863): libfprint-SSM-DEBUG: 04:24:30.949: [vfs5011] PREPARE CAPTURE entering state 13
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.949: Receiving 2368 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.982: Got 2368 bytes out of 2368
(process:17863): libfprint-SSM-DEBUG: 04:24:30.982: [vfs5011] PREPARE CAPTURE entering state 14
(process:17863): libfprint-vfs5011-DEBUG: 04:24:30.982: Receiving 64 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:31.011: Got 36 bytes out of 64
(process:17863): libfprint-SSM-DEBUG: 04:24:31.012: [vfs5011] PREPARE CAPTURE entering state 15
(process:17863): libfprint-vfs5011-DEBUG: 04:24:31.012: Receiving 4800 bytes
(process:17863): libfprint-vfs5011-DEBUG: 04:24:31.045: Got 4800 bytes out of 4800
(process:17863): libfprint-SSM-DEBUG: 04:24:31.045: [vfs5011] PREPARE CAPTURE entering state 16
(process:17863): libfprint-vfs5011-DEBUG: 04:24:31.045: Sending vfs5011_prepare_03
(process:17863): libfprint-SSM-DEBUG: 04:24:31.072: [vfs5011] PREPARE CAPTURE entering state 17
(process:17863): libfprint-vfs5011-DEBUG: 04:24:31.072: Receiving 64 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:31.109: [vfs5011] PREPARE CAPTURE entering state 18
(process:17863): libfprint-vfs5011-DEBUG: 04:24:31.109: Sending vfs5011_prepare_04
(process:17863): libfprint-SSM-DEBUG: 04:24:31.136: [vfs5011] PREPARE CAPTURE entering state 19
(process:17863): libfprint-vfs5011-DEBUG: 04:24:31.136: Receiving 2368 bytes
(process:17863): libfprint-SSM-DEBUG: 04:24:31.163: [vfs5011] PREPARE CAPTURE completed successfully
(process:17863): libfprint-SSM-DEBUG: 04:24:31.163: [vfs5011] DEV_ACTIVATE_NUM_STATES completed successfully
(process:17863): libfprint-vfs5011-DEBUG: 04:24:31.163: finishing
(process:17863): libfprint-assembling-DEBUG: 04:24:31.163: 1694838271163901
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 1
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 4
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 4
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 3
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 3
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 4
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.164: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.165: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.166: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.166: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.170: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.170: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.170: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.170: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.170: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.170: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.170: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.170: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.171: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 4
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 4
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.172: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.173: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.174: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.175: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 11
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.176: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 30
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.177: 26
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.178: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 4
(process:17863): libfprint-assembling-DEBUG: 04:24:31.179: 2
(process:17863): libfprint-assembling-DEBUG: 04:24:31.180: offsets_filtered: 1694838271180281
(process:17863): libfprint-assembling-DEBUG: 04:24:31.180: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.180: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.180: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.180: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.180: 5
(process:17863): libfprint-assembling-DEBUG: 04:24:31.180: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.180: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.180: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 27
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.181: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.182: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.182: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.182: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.189: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.189: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.189: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.189: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.189: 29
(process:17863): libfprint-assembling-DEBUG: 04:24:31.189: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.189: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 28
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.190: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 6
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.191: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.192: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.193: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.194: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 9
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.195: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 8
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.196: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 7
(process:17863): libfprint-assembling-DEBUG: 04:24:31.197: 2
(process:17863): libfprint-vfs5011-DEBUG: 04:24:31.224: Image captured, committing
(process:17863): libfprint-image_device-DEBUG: 04:24:31.225: Image device captured an image
(process:17863): libfprint-image_device-DEBUG: 04:24:31.225: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17863): libfprint-device-DEBUG: 04:24:31.225: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17863): libfprint-device-DEBUG: 04:24:31.226: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17863): libfprint-image_device-DEBUG: 04:24:31.226: Image device reported finger status: off
(process:17863): libfprint-image_device-DEBUG: 04:24:31.226: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17863): libfprint-image_device-DEBUG: 04:24:31.226: Deactivating image device
(process:17863): libfprint-image_device-DEBUG: 04:24:31.226: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17863): libfprint-image_device-DEBUG: 04:24:31.226: Image device deactivation completed
(process:17863): libfprint-image_device-DEBUG: 04:24:31.226: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17863): libfprint-image-DEBUG: 04:24:31.314: Minutiae scan completed in 0.088351 secs
(process:17863): libfprint-device-DEBUG: 04:24:31.315: Device reported capture completion
(process:17863): libfprint-device-DEBUG: 04:24:31.315: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17863): libfprint-device-DEBUG: 04:24:31.316: Updated temperature model after 1.40 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17863): libfprint-image_device-DEBUG: 04:24:31.323: Image device close completed
(process:17863): libfprint-device-DEBUG: 04:24:31.323: Device reported close completion
(process:17863): libfprint-device-DEBUG: 04:24:31.331: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17863): libfprint-device-DEBUG: 04:24:31.332: Updated temperature model after 0.02 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17860): DEBUG: 04:24:31.842: umockdev.vala:150: Removing test bed /tmp/umockdev.RTYEB2
(umockdev-run:17860): GLib-DEBUG: 04:24:31.869: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-a6y5pjet/capture.png and /<<PKGBUILDDIR>>/tests/vfs5011/capture.png
==============================================================================
================================== 104/116 ===================================
test: libfprint:drivers / goodixmoc
start time: 04:24:32
duration: 8.99s
result: exit status 0
command: MALLOC_PERTURB_=160 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DRIVERS_WHITELIST=goodixmoc /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/goodixmoc
----------------------------------- stdout -----------------------------------
** (umockdev-run:17882): DEBUG: 04:24:32.324: umockdev.vala:123: Created udev test bed /tmp/umockdev.NIH7A2
** (umockdev-run:17882): DEBUG: 04:24:32.325: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-9
** (umockdev-run:17882): DEBUG: 04:24:32.345: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-9 (subsystem usb)
** (umockdev-run:17882): DEBUG: 04:24:32.391: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.NIH7A2/dev/bus/usb/003/004
** (umockdev-run:17882): DEBUG: 04:24:32.392: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3
** (umockdev-run:17882): DEBUG: 04:24:32.419: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb)
** (umockdev-run:17882): DEBUG: 04:24:32.461: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.NIH7A2/dev/bus/usb/003/001
** (umockdev-run:17882): DEBUG: 04:24:32.462: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17882): DEBUG: 04:24:32.469: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17882): GLib-DEBUG: 04:24:32.510: pidfd_open(17885) failed with error: Function not implemented
(process:17885): libfprint-context-DEBUG: 04:24:32.876: Initializing FpContext (libfprint version 1.94.6)
(process:17885): libfprint-context-DEBUG: 04:24:33.187: No driver found for USB device 1D6B:0002
(process:17885): libfprint-device-DEBUG: 04:24:33.322: Device reported probe completion
(process:17885): libfprint-device-DEBUG: 04:24:33.322: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17885): libfprint-device-DEBUG: 04:24:33.322: Not updating temperature model, device can run continuously!
(process:17885): libfprint-SSM-DEBUG: 04:24:33.366: [goodixmoc] FP_INIT_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:33.367: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:33.397: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:33.418: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:33.451: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:33.479: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-goodixmoc-DEBUG: 04:24:33.508: Firmware type: APP
(process:17885): libfprint-goodixmoc-DEBUG: 04:24:33.508: Firmware version: 01000274
(process:17885): libfprint-SSM-DEBUG: 04:24:33.509: [goodixmoc] FP_INIT_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:33.509: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:33.526: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:33.540: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:33.565: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:33.598: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:33.622: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:33.658: [goodixmoc] FP_INIT_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:33.658: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:33.668: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:33.685: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:33.710: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:33.743: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:33.772: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:33.802: [goodixmoc] FP_INIT_NUM_STATES completed successfully
(process:17885): libfprint-device-DEBUG: 04:24:33.802: Device reported open completion
(process:17885): libfprint-SSM-DEBUG: 04:24:33.802: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-device-DEBUG: 04:24:33.802: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17885): libfprint-device-DEBUG: 04:24:33.802: Not updating temperature model, device can run continuously!
(process:17885): libfprint-SSM-DEBUG: 04:24:33.803: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:33.834: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:33.859: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:33.888: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:33.913: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-goodixmoc-DEBUG: 04:24:33.950: Successfully cleared storage
(process:17885): libfprint-device-DEBUG: 04:24:33.950: Device reported deletion completion
(process:17885): libfprint-SSM-DEBUG: 04:24:33.951: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-device-DEBUG: 04:24:33.951: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17885): libfprint-device-DEBUG: 04:24:33.951: Not updating temperature model, device can run continuously!
(process:17885): libfprint-device-DEBUG: 04:24:33.961: Not updating temperature model, device can run continuously!
(process:17885): libfprint-SSM-DEBUG: 04:24:33.961: [goodixmoc] enroll entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:33.961: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:33.988: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.013: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.046: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.071: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.102: [goodixmoc] enroll entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.102: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:34.116: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:34.134: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.162: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.191: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.216: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.249: [goodixmoc] enroll entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.249: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:34.266: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:34.280: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.313: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.346: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.370: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.407: [goodixmoc] enroll entering state 3
(process:17885): libfprint-device-DEBUG: 04:24:34.408: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:34.408: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:34.417: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:34.435: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.461: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.494: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.518: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:34.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:34.552: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:34.552: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:34.561: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:34.579: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.603: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.632: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.657: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:34.687: Device reported enroll progress, reported 1 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:34.688: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:34.688: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:34.697: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:34.707: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.729: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.753: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.773: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:34.793: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:34.794: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:34.794: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:34.803: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:34.812: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.829: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.852: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:34.868: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:34.898: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:34.898: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:34.898: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:34.908: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:34.921: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.946: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:34.979: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:35.000: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:35.024: Device reported enroll progress, reported 2 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:35.024: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:35.024: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:35.034: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:35.043: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.060: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.082: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:35.099: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:35.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:35.121: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:35.122: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:35.131: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:35.142: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.162: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.184: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:35.201: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:35.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:35.223: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:35.223: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:35.234: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:35.244: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.261: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.283: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:35.301: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:35.323: Device reported enroll progress, reported 3 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:35.323: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:35.323: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:35.333: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:35.343: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.360: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.385: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:35.401: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:35.423: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:35.423: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:35.424: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:35.434: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:35.444: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.461: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.483: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:35.501: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:35.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:35.523: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:35.524: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:35.533: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:35.543: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.561: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.585: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:35.603: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:35.624: Device reported enroll progress, reported 4 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:35.625: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:35.625: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:35.635: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:35.645: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.670: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.698: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:35.723: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:35.756: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:35.756: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:35.756: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:35.769: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:35.787: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.811: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.840: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:35.865: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:35.898: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:35.898: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:35.898: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:35.912: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:35.921: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.950: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:35.979: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:36.003: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:36.036: Device reported enroll progress, reported 5 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:36.036: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:36.036: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:36.050: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:36.067: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.088: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.121: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:36.145: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:36.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:36.179: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:36.179: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:36.188: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:36.206: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.230: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.259: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:36.286: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:36.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:36.318: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:36.318: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:36.335: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:36.344: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.367: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.403: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:36.423: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:36.455: Device reported enroll progress, reported 6 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:36.455: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:36.456: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:36.469: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:36.482: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.510: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.537: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:36.561: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:36.589: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:36.589: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:36.589: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:36.610: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:36.620: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.643: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.675: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:36.698: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:36.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:36.726: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:36.726: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:36.739: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:36.756: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.780: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.807: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:36.831: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:36.858: Device reported enroll progress, reported 7 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:36.859: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:36.859: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:36.876: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:36.885: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.908: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:36.944: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:36.967: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:36.995: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:36.995: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:36.995: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:37.005: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:37.023: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.063: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.106: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:37.138: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:37.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:37.178: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:37.178: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:37.192: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:37.214: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.262: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.302: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:37.334: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:37.378: Device reported enroll progress, reported 8 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:37.378: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:37.378: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:37.396: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:37.418: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.450: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.479: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:37.503: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:37.535: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:37.535: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:37.535: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:37.544: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:37.561: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.585: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.623: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:37.649: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:37.683: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:37.683: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:37.683: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:37.701: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:37.711: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.742: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.771: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:37.794: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:37.823: Device reported enroll progress, reported 9 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:37.823: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:37.823: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:37.836: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:37.849: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.873: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:37.909: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:37.929: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:37.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:37.962: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:37.962: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:37.979: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:37.992: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.016: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.045: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:38.068: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:38.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:38.105: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:38.105: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:38.118: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:38.135: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.160: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.189: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:38.219: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:38.246: Device reported enroll progress, reported 10 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:38.250: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:38.251: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:38.264: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:38.283: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.304: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.334: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:38.358: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:38.391: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:38.391: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:38.391: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:38.405: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:38.418: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.442: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.475: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:38.496: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:38.531: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:38.531: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:38.531: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:38.548: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:38.557: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.581: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.609: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:38.633: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:38.672: Device reported enroll progress, reported 11 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:38.672: [goodixmoc] enroll entering state 5
(process:17885): libfprint-SSM-DEBUG: 04:24:38.672: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:38.682: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:38.697: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.717: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.750: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:38.774: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:38.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:38.804: [goodixmoc] enroll entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:38.804: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:38.822: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:38.832: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.856: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:38.890: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:38.914: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:38.944: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:38.944: [goodixmoc] enroll entering state 4
(process:17885): libfprint-SSM-DEBUG: 04:24:38.944: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:38.963: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:38.977: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.001: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.029: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.053: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:39.080: Device reported enroll progress, reported 12 of 12 have been completed
(process:17885): libfprint-SSM-DEBUG: 04:24:39.081: [goodixmoc] enroll entering state 6
(process:17885): libfprint-SSM-DEBUG: 04:24:39.081: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:39.094: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:39.107: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.131: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.163: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.187: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.215: [goodixmoc] enroll entering state 7
(process:17885): libfprint-goodixmoc-DEBUG: 04:24:39.216: user_id: FP1-00000000-0-00000000-nobody, user_id_len: 30, finger: 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.216: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:39.229: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:39.242: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.265: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.297: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.321: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.353: [goodixmoc] enroll entering state 8
(process:17885): libfprint-SSM-DEBUG: 04:24:39.353: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:39.370: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:39.379: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.403: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.431: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.455: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.491: [goodixmoc] enroll completed successfully
(process:17885): libfprint-goodixmoc-DEBUG: 04:24:39.491: Enrollment complete!
(process:17885): libfprint-device-DEBUG: 04:24:39.492: Device reported enroll completion
(process:17885): libfprint-device-DEBUG: 04:24:39.492: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17885): libfprint-device-DEBUG: 04:24:39.492: Print for finger FP_FINGER_UNKNOWN enrolled
(process:17885): libfprint-SSM-DEBUG: 04:24:39.492: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-device-DEBUG: 04:24:39.492: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17885): libfprint-device-DEBUG: 04:24:39.492: Not updating temperature model, device can run continuously!
(process:17885): libfprint-goodixmoc-DEBUG: 04:24:39.493: 38977979091591: ../libfprint/drivers/goodixmoc/goodix.c:1535
(process:17885): libfprint-SSM-DEBUG: 04:24:39.493: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:39.519: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.541: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.574: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.598: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-goodixmoc-DEBUG: 04:24:39.627: Query complete!
(process:17885): libfprint-device-DEBUG: 04:24:39.627: Device reported listing completion
(process:17885): libfprint-SSM-DEBUG: 04:24:39.627: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-device-DEBUG: 04:24:39.627: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17885): libfprint-device-DEBUG: 04:24:39.627: Not updating temperature model, device can run continuously!
(process:17885): libfprint-device-DEBUG: 04:24:39.633: Not updating temperature model, device can run continuously!
(process:17885): libfprint-SSM-DEBUG: 04:24:39.633: [goodixmoc] verify entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:39.633: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:39.663: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.687: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.715: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.739: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.775: [goodixmoc] verify entering state 1
(process:17885): libfprint-device-DEBUG: 04:24:39.775: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:39.775: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:39.784: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:39.797: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.821: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.858: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.881: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:39.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:39.910: [goodixmoc] verify entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:39.910: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:39.922: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:39.936: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.962: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:39.990: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.013: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-DEBUG: 04:24:40.041: match, score: 28, study: 0
(process:17885): libfprint-device-DEBUG: 04:24:40.049: Device reported verify result
(process:17885): libfprint-SSM-DEBUG: 04:24:40.049: [goodixmoc] verify entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:40.049: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:40.066: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:40.075: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.098: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.125: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.151: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.179: [goodixmoc] verify completed successfully
(process:17885): libfprint-goodixmoc-DEBUG: 04:24:40.179: Verify complete!
(process:17885): libfprint-device-DEBUG: 04:24:40.179: Device reported verify completion
(process:17885): libfprint-device-DEBUG: 04:24:40.179: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17885): libfprint-SSM-DEBUG: 04:24:40.179: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-device-DEBUG: 04:24:40.180: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17885): libfprint-device-DEBUG: 04:24:40.180: Not updating temperature model, device can run continuously!
(process:17885): libfprint-device-DEBUG: 04:24:40.196: Not updating temperature model, device can run continuously!
(process:17885): libfprint-SSM-DEBUG: 04:24:40.196: [goodixmoc] verify entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:40.197: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:40.218: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.242: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.269: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.293: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.321: [goodixmoc] verify entering state 1
(process:17885): libfprint-device-DEBUG: 04:24:40.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17885): libfprint-SSM-DEBUG: 04:24:40.321: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:40.338: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:40.347: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.371: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.403: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.430: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-device-DEBUG: 04:24:40.458: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17885): libfprint-SSM-DEBUG: 04:24:40.458: [goodixmoc] verify entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.458: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:40.472: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:40.490: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.513: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.543: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.566: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-DEBUG: 04:24:40.594: match, score: 35, study: 0
(process:17885): libfprint-device-DEBUG: 04:24:40.603: Device reported identify result
(process:17885): libfprint-SSM-DEBUG: 04:24:40.603: [goodixmoc] verify entering state 3
(process:17885): libfprint-SSM-DEBUG: 04:24:40.603: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:40.612: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-SSM-DEBUG: 04:24:40.629: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.651: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.679: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.702: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.730: [goodixmoc] verify completed successfully
(process:17885): libfprint-goodixmoc-DEBUG: 04:24:40.730: Verify complete!
(process:17885): libfprint-device-DEBUG: 04:24:40.730: Device reported identify completion
(process:17885): libfprint-device-DEBUG: 04:24:40.730: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17885): libfprint-SSM-DEBUG: 04:24:40.730: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-device-DEBUG: 04:24:40.731: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17885): libfprint-device-DEBUG: 04:24:40.731: Not updating temperature model, device can run continuously!
(process:17885): libfprint-SSM-DEBUG: 04:24:40.737: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(process:17885): libfprint-SSM-DEBUG: 04:24:40.763: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.786: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(process:17885): libfprint-SSM-DEBUG: 04:24:40.813: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-SSM-DEBUG: 04:24:40.837: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(process:17885): libfprint-goodixmoc-DEBUG: 04:24:40.868: Successfully deleted enrolled user
(process:17885): libfprint-device-DEBUG: 04:24:40.868: Device reported deletion completion
(process:17885): libfprint-SSM-DEBUG: 04:24:40.868: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(process:17885): libfprint-device-DEBUG: 04:24:40.869: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(process:17885): libfprint-device-DEBUG: 04:24:40.869: Not updating temperature model, device can run continuously!
(process:17885): libfprint-device-DEBUG: 04:24:40.882: Device reported close completion
(process:17885): libfprint-device-DEBUG: 04:24:40.890: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17885): libfprint-device-DEBUG: 04:24:40.890: Not updating temperature model, device can run continuously!
enrolling
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 1, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 2, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 3, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 4, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 5, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 6, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 7, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 8, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 9, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 10, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 11, None, None, None)
enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf71bfac8 (FpiDeviceGoodixMoc at 0x11fb0f0)>, 12, None, None, None)
enroll done
listing
listing done
verifying
verify done
async identifying
indentification_done: <FPrint.Print object at 0xf71ce848 (FpPrint at 0x120aa18)> <FPrint.Print object at 0xf71ce868 (FpPrint at 0x120aa50)>
deleting
delete done
** (umockdev-run:17882): DEBUG: 04:24:40.946: umockdev.vala:150: Removing test bed /tmp/umockdev.NIH7A2
(umockdev-run:17882): GLib-DEBUG: 04:24:40.991: unsetenv() is not thread-safe and should not be used after threads are created
==============================================================================
================================== 105/116 ===================================
test: libfprint:drivers / nb1010
start time: 04:24:41
duration: 3.75s
result: exit status 0
command: FP_DRIVERS_WHITELIST=nb1010 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=164 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/nb1010
----------------------------------- stdout -----------------------------------
** (umockdev-run:17892): DEBUG: 04:24:41.325: umockdev.vala:123: Created udev test bed /tmp/umockdev.LBP7A2
** (umockdev-run:17892): DEBUG: 04:24:41.326: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7
** (umockdev-run:17892): DEBUG: 04:24:41.369: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb)
** (umockdev-run:17892): DEBUG: 04:24:41.410: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.LBP7A2/dev/bus/usb/001/003
** (umockdev-run:17892): DEBUG: 04:24:41.411: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1
** (umockdev-run:17892): DEBUG: 04:24:41.462: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb)
** (umockdev-run:17892): DEBUG: 04:24:41.497: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.LBP7A2/dev/bus/usb/001/001
** (umockdev-run:17892): DEBUG: 04:24:41.498: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0
** (umockdev-run:17892): DEBUG: 04:24:41.526: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci)
** (umockdev-run:17892): DEBUG: 04:24:41.566: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3
** (umockdev-run:17892): DEBUG: 04:24:41.583: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci)
(umockdev-run:17892): GLib-GIO-DEBUG: 04:24:41.630: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
(umockdev-run:17892): GLib-DEBUG: 04:24:41.654: pidfd_open(17895) failed with error: Function not implemented
(process:17895): libfprint-context-DEBUG: 04:24:42.056: Initializing FpContext (libfprint version 1.94.6)
(process:17895): libfprint-context-DEBUG: 04:24:42.086: No driver found for USB device 1D6B:0002
(process:17895): libfprint-device-DEBUG: 04:24:42.089: Device reported probe completion
(process:17895): libfprint-device-DEBUG: 04:24:42.089: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17895): libfprint-device-DEBUG: 04:24:42.089: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17895): libfprint-image_device-DEBUG: 04:24:42.142: Image device open completed
(process:17895): libfprint-device-DEBUG: 04:24:42.142: Device reported open completion
(process:17895): libfprint-nb1010-DEBUG: 04:24:42.142: nb1010 Initialized
(process:17895): libfprint-device-DEBUG: 04:24:42.142: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17895): libfprint-device-DEBUG: 04:24:42.143: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17895): libfprint-device-DEBUG: 04:24:42.144: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17895): libfprint-image_device-DEBUG: 04:24:42.144: Activating image device
(process:17895): libfprint-image_device-DEBUG: 04:24:42.145: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17895): libfprint-image_device-DEBUG: 04:24:42.145: Image device activation completed
(process:17895): libfprint-image_device-DEBUG: 04:24:42.145: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17895): libfprint-image_device-DEBUG: 04:24:42.145: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17895): libfprint-SSM-DEBUG: 04:24:42.145: [nb1010] M_LOOP_NUM_STATES entering state 0
(process:17895): libfprint-device-DEBUG: 04:24:42.145: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17895): libfprint-nb1010-DEBUG: 04:24:42.145: nb1010 Activated
(process:17895): libfprint-SSM-DEBUG: 04:24:42.194: [nb1010] M_LOOP_NUM_STATES entering state 1
(process:17895): libfprint-SSM-DEBUG: 04:24:42.242: [nb1010] M_LOOP_NUM_STATES entering state 2
(process:17895): libfprint-device-DEBUG: 04:24:42.256: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17895): libfprint-SSM-DEBUG: 04:24:42.276: [nb1010] M_LOOP_NUM_STATES entering state 3
(process:17895): libfprint-device-DEBUG: 04:24:42.276: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17895): libfprint-image_device-DEBUG: 04:24:42.276: Image device reported finger status: on
(process:17895): libfprint-image_device-DEBUG: 04:24:42.276: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17895): libfprint-SSM-DEBUG: 04:24:42.344: [nb1010] M_LOOP_NUM_STATES entering state 4
(process:17895): libfprint-SSM-DEBUG: 04:24:42.416: [nb1010] M_LOOP_NUM_STATES entering state 5
(process:17895): libfprint-SSM-DEBUG: 04:24:44.233: [nb1010] M_LOOP_NUM_STATES entering state 6
(process:17895): libfprint-image_device-DEBUG: 04:24:44.233: Image device captured an image
(process:17895): libfprint-image_device-DEBUG: 04:24:44.234: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17895): libfprint-device-DEBUG: 04:24:44.234: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17895): libfprint-SSM-DEBUG: 04:24:44.234: [nb1010] M_LOOP_NUM_STATES completed successfully
(process:17895): libfprint-nb1010-DEBUG: 04:24:44.234: nb1010 ssm complete cb
(process:17895): libfprint-device-DEBUG: 04:24:44.234: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17895): libfprint-image_device-DEBUG: 04:24:44.234: Image device reported finger status: off
(process:17895): libfprint-image_device-DEBUG: 04:24:44.235: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17895): libfprint-image_device-DEBUG: 04:24:44.235: Deactivating image device
(process:17895): libfprint-image_device-DEBUG: 04:24:44.235: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17895): libfprint-image_device-DEBUG: 04:24:44.235: Image device deactivation completed
(process:17895): libfprint-image_device-DEBUG: 04:24:44.235: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17895): libfprint-nb1010-DEBUG: 04:24:44.235: nb1010 Deactivated
(process:17895): libfprint-image-DEBUG: 04:24:44.305: Minutiae scan completed in 0.070727 secs
(process:17895): libfprint-device-DEBUG: 04:24:44.306: Device reported capture completion
(process:17895): libfprint-device-DEBUG: 04:24:44.306: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17895): libfprint-device-DEBUG: 04:24:44.306: Updated temperature model after 2.05 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17895): libfprint-image_device-DEBUG: 04:24:44.312: Image device close completed
(process:17895): libfprint-device-DEBUG: 04:24:44.312: Device reported close completion
(process:17895): libfprint-nb1010-DEBUG: 04:24:44.317: nb1010 Deinitialized
(process:17895): libfprint-device-DEBUG: 04:24:44.317: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17895): libfprint-device-DEBUG: 04:24:44.317: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17892): DEBUG: 04:24:44.586: umockdev.vala:150: Removing test bed /tmp/umockdev.LBP7A2
(umockdev-run:17892): GLib-DEBUG: 04:24:44.645: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-ey7zkw0l/capture.png and /<<PKGBUILDDIR>>/tests/nb1010/capture.png
==============================================================================
================================== 106/116 ===================================
test: libfprint:drivers / egis0570
start time: 04:24:44
duration: 14.97s
result: exit status 0
command: MALLOC_PERTURB_=67 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_DRIVERS_WHITELIST=egis0570 FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/egis0570
----------------------------------- stdout -----------------------------------
** (umockdev-run:17903): DEBUG: 04:24:44.989: umockdev.vala:123: Created udev test bed /tmp/umockdev.9OXLB2
** (umockdev-run:17903): DEBUG: 04:24:44.989: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9
** (umockdev-run:17903): DEBUG: 04:24:45.008: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb)
** (umockdev-run:17903): DEBUG: 04:24:45.044: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.9OXLB2/dev/bus/usb/001/005
** (umockdev-run:17903): DEBUG: 04:24:45.045: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17903): DEBUG: 04:24:45.055: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17903): DEBUG: 04:24:45.081: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.9OXLB2/dev/bus/usb/001/001
** (umockdev-run:17903): DEBUG: 04:24:45.083: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17903): DEBUG: 04:24:45.088: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17903): GLib-DEBUG: 04:24:45.122: pidfd_open(17906) failed with error: Function not implemented
(process:17906): libfprint-context-DEBUG: 04:24:45.538: Initializing FpContext (libfprint version 1.94.6)
(process:17906): libfprint-context-DEBUG: 04:24:45.571: No driver found for USB device 1D6B:0002
(process:17906): libfprint-device-DEBUG: 04:24:45.574: Device reported probe completion
(process:17906): libfprint-device-DEBUG: 04:24:45.575: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17906): libfprint-device-DEBUG: 04:24:45.576: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17906): libfprint-image_device-DEBUG: 04:24:45.604: Image device open completed
(process:17906): libfprint-device-DEBUG: 04:24:45.604: Device reported open completion
(process:17906): libfprint-device-DEBUG: 04:24:45.604: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17906): libfprint-device-DEBUG: 04:24:45.604: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17906): libfprint-device-DEBUG: 04:24:45.610: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17906): libfprint-image_device-DEBUG: 04:24:45.611: Activating image device
(process:17906): libfprint-image_device-DEBUG: 04:24:45.611: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17906): libfprint-SSM-DEBUG: 04:24:45.611: [egis0570] SM_STATES_NUM entering state 0
(process:17906): libfprint-SSM-DEBUG: 04:24:45.611: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:45.611: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-image_device-DEBUG: 04:24:45.616: Image device activation completed
(process:17906): libfprint-image_device-DEBUG: 04:24:45.616: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17906): libfprint-image_device-DEBUG: 04:24:45.616: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17906): libfprint-device-DEBUG: 04:24:45.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17906): libfprint-SSM-DEBUG: 04:24:45.636: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:45.646: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:45.697: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:45.711: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-device-DEBUG: 04:24:45.729: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17906): libfprint-SSM-DEBUG: 04:24:45.760: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:45.778: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:45.825: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:45.839: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:45.886: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:45.903: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:45.954: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:45.964: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.011: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.024: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.072: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.089: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.136: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.150: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.197: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.215: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.262: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.271: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.323: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.336: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.383: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.397: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.448: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.457: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.504: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.522: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.569: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.578: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.625: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.639: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.690: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.704: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.751: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.769: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.812: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.834: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.879: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.893: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:46.947: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:46.957: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.006: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.006: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-image_device-DEBUG: 04:24:47.037: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:47.038: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:47.046: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:47.047: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.075: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.086: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.134: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.147: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.178: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.189: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.221: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.221: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.243: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.243: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.243: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.243: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.244: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:47.244: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:47.244: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:47.244: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:47.244: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.264: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.274: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.308: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.318: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.351: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.361: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.392: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.392: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.414: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.414: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.414: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.414: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.414: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:47.414: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:47.414: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:47.414: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:47.414: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.436: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.445: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.477: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.486: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.517: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.527: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.558: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.558: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.581: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.581: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.581: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.581: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.581: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:47.581: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:47.581: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:47.581: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:47.582: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.601: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.611: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.644: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.654: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.686: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.695: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.727: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.727: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.749: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.749: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.749: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.749: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.749: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:47.749: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:47.749: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:47.749: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:47.750: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.768: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.778: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.809: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.819: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.851: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.860: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.892: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.892: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.914: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.914: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.914: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.914: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:47.914: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:47.914: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:47.914: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:47.915: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:47.915: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.934: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.944: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:47.976: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:47.986: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.017: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.027: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.058: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.058: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.081: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.081: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.081: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.081: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.081: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:48.081: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:48.081: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:48.081: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:48.081: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.100: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.110: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.142: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.152: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.185: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.195: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.228: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.228: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.253: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.253: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.253: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.253: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.253: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:48.253: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:48.253: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:48.253: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:48.253: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.273: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.283: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.317: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.327: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.360: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.371: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.404: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.404: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.426: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.426: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.426: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.426: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.426: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:48.426: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:48.426: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:48.426: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:48.426: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.447: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.458: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.490: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.500: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.531: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.541: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.574: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.575: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.598: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.598: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.598: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.598: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.598: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:48.598: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:48.598: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:48.598: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:48.598: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.618: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.628: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.662: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.672: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.721: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.737: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.785: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.785: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.820: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.820: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.820: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.820: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:48.820: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:48.820: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:48.820: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:48.820: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:48.821: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.845: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.863: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.912: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.926: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:48.974: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:48.989: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.036: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.037: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.067: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.067: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.068: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.068: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.068: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:49.068: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:49.068: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:49.068: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:49.068: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.100: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.119: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.163: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.177: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.225: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.243: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.284: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.285: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.313: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.314: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.314: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.314: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.318: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:49.318: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:49.318: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:49.318: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:49.318: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.345: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.362: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.404: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.418: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.465: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.482: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.524: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.524: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.558: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.558: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.558: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.558: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.558: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:49.558: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:49.558: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:49.558: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:49.558: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.589: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.606: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.652: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.669: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.708: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.717: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.758: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.758: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.779: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.779: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.779: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.779: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.779: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:49.779: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:49.780: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:49.780: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:49.780: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.803: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.812: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.842: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.851: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.885: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.895: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.925: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.925: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.947: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.947: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.947: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.947: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:49.947: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:49.947: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:49.948: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:49.948: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:49.948: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:49.970: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:49.979: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.010: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.019: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.051: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.060: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.095: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.095: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.118: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.118: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.118: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.118: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.118: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:50.119: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:50.119: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:50.119: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:50.119: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.139: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.150: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.182: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.192: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.233: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.248: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.300: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.300: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.329: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.330: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.330: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.330: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.330: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:50.330: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:50.330: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:50.330: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:50.330: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.357: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.375: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.418: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.435: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.482: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.496: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.543: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.544: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.574: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.578: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.578: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.578: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.578: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:50.578: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:50.578: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:50.578: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:50.579: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.606: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.621: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.671: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.689: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.736: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.750: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.800: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.800: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.836: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.836: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.836: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.836: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:50.836: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:50.836: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:50.836: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:50.836: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:50.837: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.867: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.881: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.933: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:50.951: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:50.999: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.008: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.055: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.056: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.089: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.089: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.090: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.090: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.090: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:51.090: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:51.090: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:51.090: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:51.090: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.117: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.136: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.183: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.196: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.243: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.257: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.304: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.304: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.338: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.338: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.338: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.338: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.338: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:51.338: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:51.339: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:51.339: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:51.339: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.362: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.371: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.419: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.437: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.484: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.497: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.546: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.547: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.587: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.587: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.587: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.588: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.588: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:51.588: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:51.588: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:51.588: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:51.588: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.613: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.631: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.676: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.695: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.758: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.798: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.870: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.870: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.911: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.911: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.911: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.911: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:51.911: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:51.912: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:51.912: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:51.912: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:51.912: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:51.943: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:51.961: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.004: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.021: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.069: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.086: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.131: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.131: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.164: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.164: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.164: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.164: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.164: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:52.165: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:52.165: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:52.165: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:52.165: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.187: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.205: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.242: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.259: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.306: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.315: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.361: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.361: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.395: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.395: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.395: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.395: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.395: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:52.395: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:52.395: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:52.395: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:52.395: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.426: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.440: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.489: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.502: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.549: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.562: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.609: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.609: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.642: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.642: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.642: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.642: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.643: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:52.643: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:52.643: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:52.643: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:52.643: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.670: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.683: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.734: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.749: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.795: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.804: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.855: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.855: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.884: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.884: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.885: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.885: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:52.885: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:52.885: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:52.885: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:52.885: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:52.885: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.916: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.929: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:52.980: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:52.989: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.036: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.050: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.096: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.096: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.134: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.134: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.134: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.134: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.134: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:53.134: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:53.134: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:53.135: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:53.135: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.163: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.177: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.224: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.237: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.284: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.297: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.342: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.342: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.371: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.371: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.371: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.371: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.372: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:53.372: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:53.372: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:53.372: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:53.372: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.402: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.419: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.460: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.473: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.520: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.533: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.578: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.578: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.611: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.611: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.611: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.611: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.611: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:53.611: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:53.611: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:53.611: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:53.611: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.641: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.650: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.695: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.703: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.732: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.742: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.773: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.773: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.795: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.795: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.795: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.795: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.795: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:53.795: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:53.795: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:53.795: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:53.795: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.814: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.823: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.854: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.863: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.894: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.903: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.933: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.934: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.954: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.955: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.955: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.955: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:53.955: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:53.955: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:53.955: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:53.955: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:53.955: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:53.974: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:53.979: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.009: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.019: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.050: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.060: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.091: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.091: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.113: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.113: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.113: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.113: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.113: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:54.113: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:54.114: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:54.114: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:54.114: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.133: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.142: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.175: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.184: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.214: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.224: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.255: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.255: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.277: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.277: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.278: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.278: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.278: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:54.278: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:54.278: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:54.278: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:54.278: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.298: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.308: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.340: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.350: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.381: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.392: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.426: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.426: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.448: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.448: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.448: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.448: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.448: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:54.448: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:54.448: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:54.448: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:54.448: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.467: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.477: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.507: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.517: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.547: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.556: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.586: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.586: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.606: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.606: Finger status (picture number, mean) : 1 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.606: Finger status (picture number, mean) : 2 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.607: Finger status (picture number, mean) : 3 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.607: Finger status (picture number, mean) : 4 , 0
(process:17906): libfprint-image_device-DEBUG: 04:24:54.607: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:54.607: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:54.607: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:54.607: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.624: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.634: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.664: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.673: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.706: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.716: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.746: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.746: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.766: Finger status (picture number, mean) : 0 , 0
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.767: Finger status (picture number, mean) : 1 , 1
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.767: Finger status (picture number, mean) : 2 , 2
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.767: Finger status (picture number, mean) : 3 , 3
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.767: Finger status (picture number, mean) : 4 , 6
(process:17906): libfprint-image_device-DEBUG: 04:24:54.767: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:54.767: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:54.767: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:54.767: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.786: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.796: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.825: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.834: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.867: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.876: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.906: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.906: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.926: Finger status (picture number, mean) : 0 , 11
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.926: Finger status (picture number, mean) : 1 , 16
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.926: Finger status (picture number, mean) : 2 , 23
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.926: Finger status (picture number, mean) : 3 , 28
(process:17906): libfprint-egis0570-DEBUG: 04:24:54.926: Finger status (picture number, mean) : 4 , 32
(process:17906): libfprint-device-DEBUG: 04:24:54.926: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17906): libfprint-image_device-DEBUG: 04:24:54.926: Image device reported finger status: on
(process:17906): libfprint-image_device-DEBUG: 04:24:54.927: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17906): libfprint-device-DEBUG: 04:24:54.927: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17906): libfprint-image_device-DEBUG: 04:24:54.927: Image device reported finger status: off
(process:17906): libfprint-SSM-DEBUG: 04:24:54.927: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:54.927: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:54.927: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.946: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.956: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:54.985: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:54.995: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.025: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.035: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.064: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.064: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.086: Finger status (picture number, mean) : 0 , 38
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.086: Finger status (picture number, mean) : 1 , 43
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.086: Finger status (picture number, mean) : 2 , 48
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.086: Finger status (picture number, mean) : 3 , 54
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.086: Finger status (picture number, mean) : 4 , 58
(process:17906): libfprint-device-DEBUG: 04:24:55.086: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17906): libfprint-image_device-DEBUG: 04:24:55.086: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:55.087: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:55.087: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:55.087: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.105: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.115: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.145: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.154: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.184: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.193: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.222: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.222: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.243: Finger status (picture number, mean) : 0 , 62
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.243: Finger status (picture number, mean) : 1 , 68
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.243: Finger status (picture number, mean) : 2 , 71
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.243: Finger status (picture number, mean) : 3 , 73
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.243: Finger status (picture number, mean) : 4 , 77
(process:17906): libfprint-image_device-DEBUG: 04:24:55.243: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:55.243: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:55.243: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:55.243: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.262: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.274: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.305: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.315: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.346: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.356: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.386: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.386: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.408: Finger status (picture number, mean) : 0 , 79
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.408: Finger status (picture number, mean) : 1 , 79
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.408: Finger status (picture number, mean) : 2 , 82
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.408: Finger status (picture number, mean) : 3 , 84
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.408: Finger status (picture number, mean) : 4 , 85
(process:17906): libfprint-image_device-DEBUG: 04:24:55.408: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:55.408: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:55.408: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:55.408: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.428: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.437: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.467: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.477: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.507: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.517: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.546: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.546: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.567: Finger status (picture number, mean) : 0 , 88
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.567: Finger status (picture number, mean) : 1 , 89
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.567: Finger status (picture number, mean) : 2 , 90
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.567: Finger status (picture number, mean) : 3 , 92
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.567: Finger status (picture number, mean) : 4 , 92
(process:17906): libfprint-image_device-DEBUG: 04:24:55.568: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:55.568: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:55.568: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:55.568: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.588: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.602: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.635: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.644: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.675: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.685: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.716: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.717: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.738: Finger status (picture number, mean) : 0 , 93
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.738: Finger status (picture number, mean) : 1 , 94
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.738: Finger status (picture number, mean) : 2 , 95
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.738: Finger status (picture number, mean) : 3 , 96
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.738: Finger status (picture number, mean) : 4 , 97
(process:17906): libfprint-image_device-DEBUG: 04:24:55.738: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:55.739: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:55.739: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:55.739: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.758: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.768: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.798: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.808: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.839: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.849: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.879: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.880: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.902: Finger status (picture number, mean) : 0 , 97
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.902: Finger status (picture number, mean) : 1 , 95
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.902: Finger status (picture number, mean) : 2 , 95
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.902: Finger status (picture number, mean) : 3 , 96
(process:17906): libfprint-egis0570-DEBUG: 04:24:55.902: Finger status (picture number, mean) : 4 , 97
(process:17906): libfprint-image_device-DEBUG: 04:24:55.902: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:55.902: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:55.902: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:55.903: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.922: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.932: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:55.963: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:55.972: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.003: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.013: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.043: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.043: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.065: Finger status (picture number, mean) : 0 , 96
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.065: Finger status (picture number, mean) : 1 , 97
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.065: Finger status (picture number, mean) : 2 , 98
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.065: Finger status (picture number, mean) : 3 , 98
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.065: Finger status (picture number, mean) : 4 , 98
(process:17906): libfprint-image_device-DEBUG: 04:24:56.065: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:56.065: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:56.065: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:56.065: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.085: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.095: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.125: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.134: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.164: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.175: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.206: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.206: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.227: Finger status (picture number, mean) : 0 , 98
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.227: Finger status (picture number, mean) : 1 , 99
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.227: Finger status (picture number, mean) : 2 , 100
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.227: Finger status (picture number, mean) : 3 , 99
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.227: Finger status (picture number, mean) : 4 , 97
(process:17906): libfprint-image_device-DEBUG: 04:24:56.228: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:56.228: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:56.228: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:56.228: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.246: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.256: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.286: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.296: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.326: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.335: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.372: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.373: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.397: Finger status (picture number, mean) : 0 , 98
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.397: Finger status (picture number, mean) : 1 , 98
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.397: Finger status (picture number, mean) : 2 , 98
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.398: Finger status (picture number, mean) : 3 , 95
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.398: Finger status (picture number, mean) : 4 , 91
(process:17906): libfprint-image_device-DEBUG: 04:24:56.398: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:56.398: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:56.398: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:56.398: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.416: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.425: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.454: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.464: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.492: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.501: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.532: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.532: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.552: Finger status (picture number, mean) : 0 , 88
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.552: Finger status (picture number, mean) : 1 , 88
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.552: Finger status (picture number, mean) : 2 , 88
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.552: Finger status (picture number, mean) : 3 , 87
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.552: Finger status (picture number, mean) : 4 , 89
(process:17906): libfprint-image_device-DEBUG: 04:24:56.552: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:56.552: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:56.552: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:56.552: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.571: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.580: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.609: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.619: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.649: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.658: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.688: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.688: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.709: Finger status (picture number, mean) : 0 , 88
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.709: Finger status (picture number, mean) : 1 , 89
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.709: Finger status (picture number, mean) : 2 , 90
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.709: Finger status (picture number, mean) : 3 , 91
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.709: Finger status (picture number, mean) : 4 , 89
(process:17906): libfprint-image_device-DEBUG: 04:24:56.709: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:56.709: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:56.709: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:56.710: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.728: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.737: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.766: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.776: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.805: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.814: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.843: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.844: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.864: Finger status (picture number, mean) : 0 , 90
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.864: Finger status (picture number, mean) : 1 , 89
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.864: Finger status (picture number, mean) : 2 , 85
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.864: Finger status (picture number, mean) : 3 , 75
(process:17906): libfprint-egis0570-DEBUG: 04:24:56.864: Finger status (picture number, mean) : 4 , 46
(process:17906): libfprint-image_device-DEBUG: 04:24:56.864: Image device reported finger status: on
(process:17906): libfprint-SSM-DEBUG: 04:24:56.864: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:56.864: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-SSM-DEBUG: 04:24:56.864: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.884: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.893: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.924: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.934: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:56.966: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:56.976: [egis0570] SM_STATES_NUM entering state 2
(process:17906): libfprint-SSM-DEBUG: 04:24:57.008: [egis0570] SM_STATES_NUM entering state 3
(process:17906): libfprint-SSM-DEBUG: 04:24:57.008: [egis0570] SM_STATES_NUM entering state 4
(process:17906): libfprint-egis0570-DEBUG: 04:24:57.030: Finger status (picture number, mean) : 0 , 17
(process:17906): libfprint-egis0570-DEBUG: 04:24:57.030: Finger status (picture number, mean) : 1 , 14
(process:17906): libfprint-egis0570-DEBUG: 04:24:57.030: Finger status (picture number, mean) : 2 , 15
(process:17906): libfprint-egis0570-DEBUG: 04:24:57.031: Finger status (picture number, mean) : 3 , 15
(process:17906): libfprint-egis0570-DEBUG: 04:24:57.031: Finger status (picture number, mean) : 4 , 15
(process:17906): libfprint-assembling-DEBUG: 04:24:57.219: calc delta completed in 0.187931 secs
(process:17906): libfprint-assembling-DEBUG: 04:24:57.387: calc delta completed in 0.168138 secs
(process:17906): libfprint-assembling-DEBUG: 04:24:57.388: errors: 10243 rev: 29954
(process:17906): libfprint-assembling-DEBUG: 04:24:57.557: calc delta completed in 0.165177 secs
(process:17906): libfprint-assembling-DEBUG: 04:24:57.557: height is 292
(process:17906): libfprint-image_device-DEBUG: 04:24:57.564: Image device captured an image
(process:17906): libfprint-image_device-DEBUG: 04:24:57.566: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
(process:17906): libfprint-device-DEBUG: 04:24:57.566: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(process:17906): libfprint-device-DEBUG: 04:24:57.567: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17906): libfprint-image_device-DEBUG: 04:24:57.567: Image device reported finger status: off
(process:17906): libfprint-image_device-DEBUG: 04:24:57.568: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17906): libfprint-image_device-DEBUG: 04:24:57.568: Deactivating image device
(process:17906): libfprint-image_device-DEBUG: 04:24:57.568: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(process:17906): libfprint-SSM-DEBUG: 04:24:57.569: [egis0570] SM_STATES_NUM entering state 5
(process:17906): libfprint-SSM-DEBUG: 04:24:57.569: [egis0570] SM_STATES_NUM entering state 1
(process:17906): libfprint-egis0570-DEBUG: 04:24:57.570: deactivating, marking completed
(process:17906): libfprint-SSM-DEBUG: 04:24:57.570: [egis0570] SM_STATES_NUM completed successfully
(process:17906): libfprint-image_device-DEBUG: 04:24:57.570: Image device deactivation completed
(process:17906): libfprint-image_device-DEBUG: 04:24:57.571: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(process:17906): libfprint-image-DEBUG: 04:24:57.830: Minutiae scan completed in 0.257760 secs
(process:17906): libfprint-device-DEBUG: 04:24:57.835: Device reported capture completion
(process:17906): libfprint-device-DEBUG: 04:24:57.836: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:17906): libfprint-device-DEBUG: 04:24:57.836: Updated temperature model after 12.11 seconds, ratio 0.27 -> 0.32, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(process:17906): libfprint-image_device-DEBUG: 04:24:57.842: Image device close completed
(process:17906): libfprint-device-DEBUG: 04:24:57.842: Device reported close completion
(process:17906): libfprint-device-DEBUG: 04:24:57.850: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17906): libfprint-device-DEBUG: 04:24:57.851: Updated temperature model after 0.01 seconds, ratio 0.32 -> 0.32, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
** (umockdev-run:17903): DEBUG: 04:24:59.298: umockdev.vala:150: Removing test bed /tmp/umockdev.9OXLB2
(umockdev-run:17903): GLib-DEBUG: 04:24:59.358: unsetenv() is not thread-safe and should not be used after threads are created
Comparing PNGs /tmp/libfprint-umockdev-test-6tl5uuxb/capture.png and /<<PKGBUILDDIR>>/tests/egis0570/capture.png
==============================================================================
================================== 107/116 ===================================
test: libfprint:drivers / fpcmoc
start time: 04:24:59
duration: 4.19s
result: exit status 0
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all FP_DRIVERS_WHITELIST=fpcmoc G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=252 /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/fpcmoc
----------------------------------- stdout -----------------------------------
** (umockdev-run:17914): DEBUG: 04:24:59.989: umockdev.vala:123: Created udev test bed /tmp/umockdev.W2ULB2
** (umockdev-run:17914): DEBUG: 04:24:59.989: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-1
** (umockdev-run:17914): DEBUG: 04:25:00.010: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-1 (subsystem usb)
** (umockdev-run:17914): DEBUG: 04:25:00.058: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.W2ULB2/dev/bus/usb/001/019
** (umockdev-run:17914): DEBUG: 04:25:00.060: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17914): DEBUG: 04:25:00.081: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17914): DEBUG: 04:25:00.117: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.W2ULB2/dev/bus/usb/001/001
** (umockdev-run:17914): DEBUG: 04:25:00.119: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17914): DEBUG: 04:25:00.133: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17914): GLib-DEBUG: 04:25:00.168: pidfd_open(17917) failed with error: Function not implemented
(process:17917): libfprint-context-DEBUG: 04:25:00.445: Initializing FpContext (libfprint version 1.94.6)
(process:17917): libfprint-DEBUG: 04:25:00.466: fpi_device_fpcmoc_init enter -->
(process:17917): libfprint-DEBUG: 04:25:00.466: 38978000063907: ../libfprint/drivers/fpcmoc/fpc.c:1854
(process:17917): libfprint-context-DEBUG: 04:25:00.467: No driver found for USB device 1D6B:0002
(process:17917): libfprint-DEBUG: 04:25:00.471: fpc_dev_probe enter -->
(process:17917): libfprint-DEBUG: 04:25:00.573: Device name: FPC L:0001 FW:127010
(process:17917): libfprint-device-DEBUG: 04:25:00.590: Device reported probe completion
(process:17917): libfprint-device-DEBUG: 04:25:00.590: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17917): libfprint-device-DEBUG: 04:25:00.591: Not updating temperature model, device can run continuously!
(process:17917): libfprint-DEBUG: 04:25:00.608: fpc_dev_open enter -->
(process:17917): libfprint-SSM-DEBUG: 04:25:00.626: [fpcmoc] FP_INIT_NUM_STATES entering state 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.626: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.626: fpc_send_ctrl_cmd CMD: 0x1, value: 0x1, index: 0 type: 2
(process:17917): libfprint-DEBUG: 04:25:00.644: fpc_cmd_receive_cb current ssm request: 1 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.645: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:00.667: fpc_cmd_receive_cb current ssm request: 1 state: 1
(process:17917): libfprint-DEBUG: 04:25:00.667: fpc_cmd_receive_cb recv evt data length: 38
(process:17917): libfprint-DEBUG: 04:25:00.667: fpc_evt_cb INIT: status=0, Sensor = 1523, HWID = 0x1711, WxH = 96 x 96
(process:17917): libfprint-DEBUG: 04:25:00.667: fpc_evt_cb INIT: FW version: 1.27.0.10
(process:17917): libfprint-SSM-DEBUG: 04:25:00.667: [fpcmoc] FP_INIT_NUM_STATES entering state 1
(process:17917): libfprint-SSM-DEBUG: 04:25:00.667: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.667: fpc_send_ctrl_cmd CMD: 0x60, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:00.677: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:00.690: fpc_cmd_receive_cb current ssm request: 96 state: 0
(process:17917): libfprint-DEBUG: 04:25:00.690: fpc_init_load_db_cb got dbid size: 16
(process:17917): libfprint-DEBUG: 04:25:00.690: fpc_init_load_db_cb dbid: 0xa981b581-adfc-e643-a0d0-88c2138092f7
(process:17917): libfprint-SSM-DEBUG: 04:25:00.690: [fpcmoc] FP_INIT_NUM_STATES completed successfully
(process:17917): libfprint-device-DEBUG: 04:25:00.691: Device reported open completion
(process:17917): libfprint-SSM-DEBUG: 04:25:00.691: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-device-DEBUG: 04:25:00.691: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17917): libfprint-device-DEBUG: 04:25:00.691: Not updating temperature model, device can run continuously!
(process:17917): libfprint-DEBUG: 04:25:00.692: fpc_dev_clear_storage enter -->
(process:17917): libfprint-SSM-DEBUG: 04:25:00.693: [fpcmoc] Clear storage entering state 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.693: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.693: fpc_send_ctrl_cmd CMD: 0x62, value: 0x0, index: 0 type: 1
(process:17917): libfprint-DEBUG: 04:25:00.712: fpc_cmd_receive_cb current ssm request: 98 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.712: [fpcmoc] Clear storage entering state 1
(process:17917): libfprint-SSM-DEBUG: 04:25:00.712: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.712: fpc_send_ctrl_cmd CMD: 0x60, value: 0x1, index: 0 type: 1
(process:17917): libfprint-SSM-DEBUG: 04:25:00.722: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:00.733: fpc_cmd_receive_cb current ssm request: 96 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.733: [fpcmoc] Clear storage completed successfully
(process:17917): libfprint-DEBUG: 04:25:00.733: Clear Storage complete!
(process:17917): libfprint-device-DEBUG: 04:25:00.733: Device reported deletion completion
(process:17917): libfprint-SSM-DEBUG: 04:25:00.733: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-device-DEBUG: 04:25:00.734: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(process:17917): libfprint-device-DEBUG: 04:25:00.734: Not updating temperature model, device can run continuously!
(process:17917): libfprint-device-DEBUG: 04:25:00.740: Not updating temperature model, device can run continuously!
(process:17917): libfprint-DEBUG: 04:25:00.740: fpc_dev_enroll enter -->
(process:17917): libfprint-SSM-DEBUG: 04:25:00.740: [fpcmoc] enroll entering state 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.740: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.740: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2
(process:17917): libfprint-DEBUG: 04:25:00.759: fpc_cmd_receive_cb current ssm request: 112 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.759: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:00.781: fpc_cmd_receive_cb current ssm request: 112 state: 1
(process:17917): libfprint-DEBUG: 04:25:00.781: fpc_cmd_receive_cb recv evt data length: 790
(process:17917): libfprint-DEBUG: 04:25:00.781: fpc_evt_cb Enum Fids: status = 0, NumFids = 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.782: [fpcmoc] enroll entering state 1
(process:17917): libfprint-SSM-DEBUG: 04:25:00.782: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.782: fpc_send_ctrl_cmd CMD: 0x67, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:00.792: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:00.802: fpc_cmd_receive_cb current ssm request: 103 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.803: [fpcmoc] enroll entering state 2
(process:17917): libfprint-device-DEBUG: 04:25:00.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:00.803: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.803: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:00.813: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:00.823: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.823: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:00.845: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:00.845: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:00.845: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:00.845: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:00.845: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:00.845: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.845: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:00.855: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:00.863: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.863: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:00.885: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:00.885: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:00.885: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:00.885: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:00.885: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:00.886: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.886: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:00.896: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:00.908: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:00.908: Enrol Update status: 1, remaining: 11
(process:17917): libfprint-device-DEBUG: 04:25:00.908: Device reported enroll progress, reported 1 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:00.909: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:00.909: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.909: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:00.919: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:00.930: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.930: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:00.951: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:00.951: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:00.951: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:00.951: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:00.951: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:00.951: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.951: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:00.961: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:00.969: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:00.969: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:00.991: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:00.991: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:00.991: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:00.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:00.991: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:00.991: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:00.991: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.001: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.013: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:01.013: Enrol Update status: 1, remaining: 10
(process:17917): libfprint-device-DEBUG: 04:25:01.013: Device reported enroll progress, reported 2 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:01.014: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.014: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.014: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.024: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.033: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.034: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.054: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.054: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:01.054: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:01.055: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:01.055: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.055: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.055: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.064: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.071: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.071: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.096: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.096: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:01.096: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:01.096: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:01.096: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:01.096: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.096: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.105: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.116: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:01.116: Enrol Update status: 1, remaining: 9
(process:17917): libfprint-device-DEBUG: 04:25:01.116: Device reported enroll progress, reported 3 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:01.117: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.117: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.117: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.125: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.134: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.134: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.155: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.155: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:01.155: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:01.155: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:01.155: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.155: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.155: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.164: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.171: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.171: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.191: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.191: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:01.191: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:01.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:01.191: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:01.191: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.191: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.200: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.212: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:01.212: Enrol Update status: 1, remaining: 8
(process:17917): libfprint-device-DEBUG: 04:25:01.212: Device reported enroll progress, reported 4 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:01.212: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.212: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.212: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.221: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.230: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.230: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.251: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.251: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:01.251: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:01.251: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:01.251: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.252: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.252: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.260: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.267: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.267: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.290: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.290: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:01.290: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:01.290: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:01.290: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:01.290: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.291: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.299: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.311: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:01.311: Enrol Update status: 1, remaining: 7
(process:17917): libfprint-device-DEBUG: 04:25:01.312: Device reported enroll progress, reported 5 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:01.312: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.312: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.312: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.321: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.330: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.330: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.350: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.351: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:01.351: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:01.351: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:01.351: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.351: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.351: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.360: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.367: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.367: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.386: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.386: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:01.386: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:01.387: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:01.387: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:01.387: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.387: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.396: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.407: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:01.407: Enrol Update status: 5, remaining: 7
(process:17917): libfprint-DEBUG: 04:25:01.407: Sample overlapping ratio is too High
(process:17917): libfprint-device-DEBUG: 04:25:01.407: Device reported enroll progress, reported 5 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:01.407: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.407: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.407: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.416: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.429: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.429: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.449: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.449: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:01.449: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:01.449: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:01.449: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.450: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.450: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.459: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.466: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.466: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.487: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.487: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:01.487: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:01.487: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:01.487: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:01.487: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.487: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.497: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.509: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:01.509: Enrol Update status: 1, remaining: 6
(process:17917): libfprint-device-DEBUG: 04:25:01.509: Device reported enroll progress, reported 6 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:01.509: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.509: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.510: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.551: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.578: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.578: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.642: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.642: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:01.642: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:01.642: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:01.643: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.643: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.643: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.660: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.676: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.677: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.720: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.720: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:01.720: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:01.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:01.720: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:01.721: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.721: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.748: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.769: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:01.769: Enrol Update status: 1, remaining: 5
(process:17917): libfprint-device-DEBUG: 04:25:01.769: Device reported enroll progress, reported 7 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:01.769: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.769: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.769: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.796: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.813: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.813: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.860: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.861: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:01.861: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:01.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:01.861: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.861: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.861: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.878: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.894: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:01.894: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:01.940: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:01.940: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:01.940: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:01.940: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:01.940: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:01.941: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.941: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:01.959: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:01.989: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:01.989: Enrol Update status: 5, remaining: 5
(process:17917): libfprint-DEBUG: 04:25:01.989: Sample overlapping ratio is too High
(process:17917): libfprint-device-DEBUG: 04:25:01.989: Device reported enroll progress, reported 7 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:01.989: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:01.989: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:01.990: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.007: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.034: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.034: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.082: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.082: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:02.082: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:02.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:02.083: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.083: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.083: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.108: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.132: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.132: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.169: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.169: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:02.169: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:02.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:02.169: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:02.169: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.169: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.188: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.204: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:02.204: Enrol Update status: 1, remaining: 4
(process:17917): libfprint-device-DEBUG: 04:25:02.204: Device reported enroll progress, reported 8 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:02.205: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.205: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.205: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.224: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.242: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.242: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.277: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.277: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:02.277: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:02.277: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:02.277: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.278: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.278: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.296: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.307: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.307: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.342: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.342: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:02.343: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:02.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:02.343: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:02.343: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.343: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.358: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.378: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:02.378: Enrol Update status: 1, remaining: 3
(process:17917): libfprint-device-DEBUG: 04:25:02.379: Device reported enroll progress, reported 9 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:02.379: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.379: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.379: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.394: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.408: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.408: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.459: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.459: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:02.459: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:02.459: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:02.459: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.459: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.459: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.469: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.485: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.485: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.523: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.523: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:02.523: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:02.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:02.523: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:02.523: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.523: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.542: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.561: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:02.562: Enrol Update status: 1, remaining: 2
(process:17917): libfprint-device-DEBUG: 04:25:02.562: Device reported enroll progress, reported 10 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:02.562: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.562: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.562: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.579: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.589: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.589: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.624: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.624: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:02.624: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:02.624: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:02.625: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.625: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.625: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.636: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.646: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.646: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.676: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.676: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:02.676: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:02.676: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:02.676: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:02.676: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.676: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.690: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.702: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:02.702: Enrol Update status: 5, remaining: 2
(process:17917): libfprint-DEBUG: 04:25:02.702: Sample overlapping ratio is too High
(process:17917): libfprint-device-DEBUG: 04:25:02.702: Device reported enroll progress, reported 10 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:02.702: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.703: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.703: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.712: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.722: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.722: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.744: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.744: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:02.744: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:02.744: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:02.744: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.744: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.744: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.754: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.769: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.769: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.806: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.806: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:02.806: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:02.806: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:02.807: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:02.807: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.807: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.816: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.836: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:02.836: Enrol Update status: 1, remaining: 1
(process:17917): libfprint-device-DEBUG: 04:25:02.836: Device reported enroll progress, reported 11 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:02.836: [fpcmoc] enroll entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.836: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.836: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.854: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.867: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.867: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.905: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.905: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:02.905: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:02.905: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:02.905: [fpcmoc] enroll entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.905: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.905: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:02.923: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:02.935: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:02.935: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:02.972: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:02.973: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:02.973: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:02.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:02.973: [fpcmoc] enroll entering state 4
(process:17917): libfprint-SSM-DEBUG: 04:25:02.973: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:02.973: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:02.991: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.000: fpc_cmd_receive_cb current ssm request: 104 state: 0
(process:17917): libfprint-DEBUG: 04:25:03.000: Enrol Update status: 0, remaining: 0
(process:17917): libfprint-device-DEBUG: 04:25:03.000: Device reported enroll progress, reported 12 of 25 have been completed
(process:17917): libfprint-SSM-DEBUG: 04:25:03.001: [fpcmoc] enroll entering state 5
(process:17917): libfprint-SSM-DEBUG: 04:25:03.001: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.001: fpc_send_ctrl_cmd CMD: 0x69, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:03.018: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.035: fpc_cmd_receive_cb current ssm request: 105 state: 0
(process:17917): libfprint-DEBUG: 04:25:03.036: Enrol End status: 0, fid: 0x0
(process:17917): libfprint-SSM-DEBUG: 04:25:03.036: [fpcmoc] enroll entering state 6
(process:17917): libfprint-SSM-DEBUG: 04:25:03.036: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.036: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:03.060: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.079: fpc_cmd_receive_cb current ssm request: 107 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:03.079: [fpcmoc] enroll entering state 7
(process:17917): libfprint-DEBUG: 04:25:03.080: user_id: FP1-00000000-0-00000000-nobody, finger: 0xf5
(process:17917): libfprint-SSM-DEBUG: 04:25:03.080: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.080: fpc_send_ctrl_cmd CMD: 0x6a, value: 0x0, index: 0 type: 1
(process:17917): libfprint-SSM-DEBUG: 04:25:03.097: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.115: fpc_cmd_receive_cb current ssm request: 106 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:03.115: [fpcmoc] enroll entering state 8
(process:17917): libfprint-SSM-DEBUG: 04:25:03.115: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.115: fpc_send_ctrl_cmd CMD: 0x61, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:03.132: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.150: fpc_cmd_receive_cb current ssm request: 97 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:03.150: [fpcmoc] enroll entering state 9
(process:17917): libfprint-SSM-DEBUG: 04:25:03.150: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.150: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1
(process:17917): libfprint-SSM-DEBUG: 04:25:03.160: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.174: fpc_cmd_receive_cb current ssm request: 3 state: 0
(process:17917): libfprint-DEBUG: 04:25:03.175: fpc_do_abort_cb Do abort for reasons
(process:17917): libfprint-SSM-DEBUG: 04:25:03.175: [fpcmoc] enroll entering state 10
(process:17917): libfprint-SSM-DEBUG: 04:25:03.175: [fpcmoc] enroll completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.175: Enrollment complete!
(process:17917): libfprint-device-DEBUG: 04:25:03.175: Device reported enroll completion
(process:17917): libfprint-device-DEBUG: 04:25:03.175: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17917): libfprint-device-DEBUG: 04:25:03.175: Print for finger FP_FINGER_UNKNOWN enrolled
(process:17917): libfprint-SSM-DEBUG: 04:25:03.175: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-device-DEBUG: 04:25:03.176: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:17917): libfprint-device-DEBUG: 04:25:03.176: Not updating temperature model, device can run continuously!
(process:17917): libfprint-DEBUG: 04:25:03.177: fpc_dev_template_list enter -->
(process:17917): libfprint-SSM-DEBUG: 04:25:03.177: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.177: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2
(process:17917): libfprint-DEBUG: 04:25:03.208: fpc_cmd_receive_cb current ssm request: 112 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:03.208: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:03.240: fpc_cmd_receive_cb current ssm request: 112 state: 1
(process:17917): libfprint-DEBUG: 04:25:03.241: fpc_cmd_receive_cb recv evt data length: 790
(process:17917): libfprint-DEBUG: 04:25:03.241: Query templates complete!
(process:17917): libfprint-device-DEBUG: 04:25:03.241: Device reported listing completion
(process:17917): libfprint-SSM-DEBUG: 04:25:03.242: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-device-DEBUG: 04:25:03.251: Completing action FPI_DEVICE_ACTION_LIST in idle!
(process:17917): libfprint-device-DEBUG: 04:25:03.251: Not updating temperature model, device can run continuously!
(process:17917): libfprint-device-DEBUG: 04:25:03.255: Not updating temperature model, device can run continuously!
(process:17917): libfprint-DEBUG: 04:25:03.255: fpc_dev_verify_identify enter -->
(process:17917): libfprint-SSM-DEBUG: 04:25:03.256: [fpcmoc] verify_identify entering state 0
(process:17917): libfprint-device-DEBUG: 04:25:03.256: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:03.256: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.256: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-DEBUG: 04:25:03.290: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:03.290: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:03.326: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:03.326: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:03.326: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:03.326: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:03.326: [fpcmoc] verify_identify entering state 1
(process:17917): libfprint-SSM-DEBUG: 04:25:03.326: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.326: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:03.336: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.347: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:03.347: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:03.380: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:03.380: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:03.380: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:03.380: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:03.380: [fpcmoc] verify_identify entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:03.381: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.381: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:03.402: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.418: fpc_cmd_receive_cb current ssm request: 107 state: 0
(process:17917): libfprint-device-DEBUG: 04:25:03.421: Device reported verify result
(process:17917): libfprint-SSM-DEBUG: 04:25:03.421: [fpcmoc] verify_identify entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:03.421: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.421: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1
(process:17917): libfprint-SSM-DEBUG: 04:25:03.435: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.446: fpc_cmd_receive_cb current ssm request: 3 state: 0
(process:17917): libfprint-DEBUG: 04:25:03.446: fpc_do_abort_cb Do abort for reasons
(process:17917): libfprint-SSM-DEBUG: 04:25:03.446: [fpcmoc] verify_identify completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.446: Verify_identify complete!
(process:17917): libfprint-device-DEBUG: 04:25:03.446: Device reported verify completion
(process:17917): libfprint-device-DEBUG: 04:25:03.446: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17917): libfprint-SSM-DEBUG: 04:25:03.447: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-device-DEBUG: 04:25:03.447: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(process:17917): libfprint-device-DEBUG: 04:25:03.447: Not updating temperature model, device can run continuously!
(process:17917): libfprint-device-DEBUG: 04:25:03.462: Not updating temperature model, device can run continuously!
(process:17917): libfprint-DEBUG: 04:25:03.463: fpc_dev_verify_identify enter -->
(process:17917): libfprint-SSM-DEBUG: 04:25:03.463: [fpcmoc] verify_identify entering state 0
(process:17917): libfprint-device-DEBUG: 04:25:03.463: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:03.463: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.463: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2
(process:17917): libfprint-DEBUG: 04:25:03.490: fpc_cmd_receive_cb current ssm request: 2 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:03.490: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:03.528: fpc_cmd_receive_cb current ssm request: 2 state: 1
(process:17917): libfprint-DEBUG: 04:25:03.528: fpc_cmd_receive_cb recv evt data length: 12
(process:17917): libfprint-DEBUG: 04:25:03.528: fpc_evt_cb Got finger down event
(process:17917): libfprint-device-DEBUG: 04:25:03.528: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17917): libfprint-SSM-DEBUG: 04:25:03.528: [fpcmoc] verify_identify entering state 1
(process:17917): libfprint-SSM-DEBUG: 04:25:03.528: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.528: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2
(process:17917): libfprint-SSM-DEBUG: 04:25:03.554: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.566: fpc_cmd_receive_cb current ssm request: 9 state: 0
(process:17917): libfprint-SSM-DEBUG: 04:25:03.566: [fpcmoc] FP_CMD_NUM_STATES entering state 1
(process:17917): libfprint-DEBUG: 04:25:03.599: fpc_cmd_receive_cb current ssm request: 9 state: 1
(process:17917): libfprint-DEBUG: 04:25:03.599: fpc_cmd_receive_cb recv evt data length: 24
(process:17917): libfprint-DEBUG: 04:25:03.599: fpc_evt_cb Got capture event
(process:17917): libfprint-device-DEBUG: 04:25:03.600: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17917): libfprint-SSM-DEBUG: 04:25:03.600: [fpcmoc] verify_identify entering state 2
(process:17917): libfprint-SSM-DEBUG: 04:25:03.600: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.600: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3
(process:17917): libfprint-SSM-DEBUG: 04:25:03.617: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.637: fpc_cmd_receive_cb current ssm request: 107 state: 0
(process:17917): libfprint-device-DEBUG: 04:25:03.640: Device reported identify result
(process:17917): libfprint-SSM-DEBUG: 04:25:03.640: [fpcmoc] verify_identify entering state 3
(process:17917): libfprint-SSM-DEBUG: 04:25:03.640: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.640: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1
(process:17917): libfprint-SSM-DEBUG: 04:25:03.657: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.673: fpc_cmd_receive_cb current ssm request: 3 state: 0
(process:17917): libfprint-DEBUG: 04:25:03.673: fpc_do_abort_cb Do abort for reasons
(process:17917): libfprint-SSM-DEBUG: 04:25:03.673: [fpcmoc] verify_identify completed successfully
(process:17917): libfprint-DEBUG: 04:25:03.673: Verify_identify complete!
(process:17917): libfprint-device-DEBUG: 04:25:03.673: Device reported identify completion
(process:17917): libfprint-device-DEBUG: 04:25:03.673: Device reported finger status change: FP_FINGER_STATUS_NONE
(process:17917): libfprint-SSM-DEBUG: 04:25:03.673: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-device-DEBUG: 04:25:03.674: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(process:17917): libfprint-device-DEBUG: 04:25:03.674: Not updating temperature model, device can run continuously!
(process:17917): libfprint-DEBUG: 04:25:03.679: fpc_dev_template_delete enter -->
(process:17917): libfprint-SSM-DEBUG: 04:25:03.680: [fpcmoc] FP_CMD_NUM_STATES entering state 0
(process:17917): libfprint-DEBUG: 04:25:03.680: fpc_send_ctrl_cmd CMD: 0x63, value: 0x0, index: 0 type: 1
(process:17917): libfprint-DEBUG: 04:25:03.693: fpc_dev_template_delete exit <--
(process:17917): libfprint-DEBUG: 04:25:03.711: fpc_cmd_receive_cb current ssm request: 99 state: 0
(process:17917): libfprint-device-DEBUG: 04:25:03.711: Device reported deletion completion
(process:17917): libfprint-SSM-DEBUG: 04:25:03.711: [fpcmoc] FP_CMD_NUM_STATES completed successfully
(process:17917): libfprint-device-DEBUG: 04:25:03.711: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(process:17917): libfprint-device-DEBUG: 04:25:03.712: Not updating temperature model, device can run continuously!
(process:17917): libfprint-DEBUG: 04:25:03.712: fpc_dev_close enter -->
(process:17917): libfprint-device-DEBUG: 04:25:03.725: Device reported close completion
(process:17917): libfprint-device-DEBUG: 04:25:03.738: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:17917): libfprint-device-DEBUG: 04:25:03.738: Not updating temperature model, device can run continuously!
Clear
Clear done
enrolling
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 1, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 2, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 3, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 4, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 5, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 5, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3))
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 6, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 7, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 7, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3))
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 8, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 9, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 10, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 10, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3))
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 11, None, None, None)
enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf6e6fb48 (FpiDeviceFpcMoc at 0x18570c0)>, 12, None, None, None)
enroll done
listing
listing done
verifying
verify done
async identifying
indentification_done: <FPrint.Print object at 0xf6e7e848 (FpPrint at 0x1866818)> <FPrint.Print object at 0xf6e7e868 (FpPrint at 0x1866850)>
deleting
delete done
** (umockdev-run:17914): DEBUG: 04:25:03.810: umockdev.vala:150: Removing test bed /tmp/umockdev.W2ULB2
(umockdev-run:17914): GLib-DEBUG: 04:25:03.898: unsetenv() is not thread-safe and should not be used after threads are created
==============================================================================
================================== 108/116 ===================================
test: libfprint:drivers / aes2501
start time: 04:24:06
duration: 75.08s
result: killed by signal 15 SIGTERM
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=49 G_MESSAGES_DEBUG=all FP_DRIVERS_WHITELIST=aes2501 G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/aes2501
----------------------------------- stdout -----------------------------------
** (umockdev-run:17711): DEBUG: 04:24:06.392: umockdev.vala:123: Created udev test bed /tmp/umockdev.WZC6A2
** (umockdev-run:17711): DEBUG: 04:24:06.393: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10
** (umockdev-run:17711): DEBUG: 04:24:06.421: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb)
** (umockdev-run:17711): DEBUG: 04:24:06.467: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.WZC6A2/dev/bus/usb/001/044
** (umockdev-run:17711): DEBUG: 04:24:06.468: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17711): DEBUG: 04:24:06.498: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17711): DEBUG: 04:24:06.531: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.WZC6A2/dev/bus/usb/001/001
** (umockdev-run:17711): DEBUG: 04:24:06.533: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17711): DEBUG: 04:24:06.538: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17711): GLib-DEBUG: 04:24:06.591: pidfd_open(17718) failed with error: Function not implemented
(process:17718): libfprint-context-DEBUG: 04:24:07.002: Initializing FpContext (libfprint version 1.94.6)
(process:17718): libfprint-context-DEBUG: 04:24:07.043: No driver found for USB device 1D6B:0002
(process:17718): libfprint-device-DEBUG: 04:24:07.045: Device reported probe completion
(process:17718): libfprint-device-DEBUG: 04:24:07.045: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17718): libfprint-device-DEBUG: 04:24:07.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17718): libfprint-image_device-DEBUG: 04:24:07.094: Image device open completed
(process:17718): libfprint-device-DEBUG: 04:24:07.094: Device reported open completion
(process:17718): libfprint-device-DEBUG: 04:24:07.094: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17718): libfprint-device-DEBUG: 04:24:07.095: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17718): libfprint-device-DEBUG: 04:24:07.096: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17718): libfprint-image_device-DEBUG: 04:24:07.097: Activating image device
(process:17718): libfprint-image_device-DEBUG: 04:24:07.097: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17718): libfprint-SSM-DEBUG: 04:24:07.097: [aes2501] ACTIVATE_NUM_STATES entering state 0
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.097: write 38 regs
(process:17718): libfprint-device-DEBUG: 04:24:07.207: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.264: all registers written
(process:17718): libfprint-SSM-DEBUG: 04:24:07.264: [aes2501] ACTIVATE_NUM_STATES entering state 1
(process:17718): libfprint-aes2501-DEBUG: 04:24:07.264: read data 1
(process:17718): libfprint-SSM-DEBUG: 04:24:07.291: [aes2501] ACTIVATE_NUM_STATES entering state 2
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.291: write 7 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.320: all registers written
(process:17718): libfprint-SSM-DEBUG: 04:24:07.320: [aes2501] ACTIVATE_NUM_STATES entering state 3
(process:17718): libfprint-aes2501-DEBUG: 04:24:07.321: 38977946918763: ../libfprint/drivers/aes2501.c:140
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.321: write 1 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.354: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:07.386: reg 0xaf = 20
(process:17718): libfprint-SSM-DEBUG: 04:24:07.386: [aes2501] ACTIVATE_NUM_STATES entering state 5
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.386: write 7 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.411: all registers written
(process:17718): libfprint-SSM-DEBUG: 04:24:07.411: [aes2501] ACTIVATE_NUM_STATES entering state 6
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.411: write 16 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.432: all registers written
(process:17718): libfprint-SSM-DEBUG: 04:24:07.432: [aes2501] ACTIVATE_NUM_STATES completed successfully
(process:17718): libfprint-image_device-DEBUG: 04:24:07.433: Image device activation completed
(process:17718): libfprint-image_device-DEBUG: 04:24:07.433: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17718): libfprint-image_device-DEBUG: 04:24:07.433: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17718): libfprint-device-DEBUG: 04:24:07.433: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17718): libfprint-aes2501-DEBUG: 04:24:07.433: 38977947031404: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.433: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.517: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:07.559: 38977947157654: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.560: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.653: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:07.686: 38977947284069: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.686: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.778: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:07.809: 38977947407473: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.809: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.910: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:07.943: 38977947540994: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:07.943: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.041: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:08.078: 38977947676236: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.078: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.170: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:08.197: 38977947795705: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.198: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.289: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:08.321: 38977947918934: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.321: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.409: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:08.444: 38977948042045: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.444: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.529: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:08.566: 38977948164528: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.566: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.651: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:08.684: 38977948282481: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.684: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.777: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:08.810: 38977948408063: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.810: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.887: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:08.919: 38977948517086: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:08.919: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.000: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:09.028: 38977948626450: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.028: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.109: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:09.142: 38977948740019: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.142: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.226: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:09.255: 38977948853055: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.255: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.334: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:09.367: 38977948964971: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.367: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.445: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:09.473: 38977949071414: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.473: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.560: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:09.597: 38977949194951: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.597: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.685: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:09.719: 38977949316765: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.719: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.818: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:09.851: 38977949448940: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.851: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.948: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:09.975: 38977949573566: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:09.975: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.059: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:10.092: 38977949690407: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.092: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.181: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:10.209: 38977949806789: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.209: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.295: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:10.327: 38977949925473: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.327: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.417: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:10.449: 38977950047595: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.450: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.539: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:10.573: 38977950171009: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.573: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.668: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:10.704: 38977950301938: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.704: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.800: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:10.836: 38977950433891: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.836: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.936: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:10.967: 38977950565648: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:10.968: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.058: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:11.094: 38977950691896: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.094: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.188: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:11.220: 38977950818187: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.220: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.309: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:11.344: 38977950942602: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.345: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.435: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:11.471: 38977951069469: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.471: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.557: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:11.597: 38977951195363: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.597: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.694: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:11.726: 38977951323960: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.726: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.814: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:11.842: 38977951440091: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.842: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.928: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:11.959: 38977951557573: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:11.959: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.039: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:12.073: 38977951670800: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.073: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.158: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:12.190: 38977951788519: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.190: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.268: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:12.299: 38977951896884: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.299: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.378: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:12.404: 38977952002709: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.405: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.486: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:12.522: 38977952111989: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.522: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.595: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:12.639: 38977952237441: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.639: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.742: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:12.778: 38977952376528: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.778: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.856: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:12.878: 38977952476210: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.878: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.956: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:12.993: 38977952591305: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:12.993: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.137: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:13.170: 38977952768529: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.170: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.258: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:13.291: 38977952888815: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.291: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.387: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:13.415: 38977953012811: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.415: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.500: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:13.532: 38977953130151: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.532: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.633: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:13.669: 38977953267176: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.669: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.766: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:13.814: 38977953412277: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.814: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.929: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:13.965: 38977953563470: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:13.965: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.054: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:14.090: 38977953688594: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.090: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.171: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:14.200: 38977953797924: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.200: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.284: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:14.313: 38977953911317: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.313: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.393: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:14.426: 38977954024413: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.426: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.515: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:14.543: 38977954141494: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.543: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.626: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:14.678: 38977954276120: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.678: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.794: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:14.827: 38977954424775: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.827: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.914: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:14.942: 38977954540571: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:14.942: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.030: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:15.067: 38977954665567: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.067: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.151: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:15.184: 38977954782101: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.184: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.267: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:15.300: 38977954898297: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.300: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.388: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:15.416: 38977955014541: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.416: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.496: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:15.533: 38977955131307: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.533: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.613: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:15.641: 38977955239519: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.641: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.724: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:15.756: 38977955354686: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.757: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.840: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:15.872: 38977955470633: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.873: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.936: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:15.973: 38977955570966: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:15.973: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.082: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:16.118: 38977955716205: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.118: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.223: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:16.261: 38977955859608: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.262: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.365: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:16.404: 38977956001900: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.404: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.510: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:16.548: 38977956146163: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.548: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.644: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:16.665: 38977956263279: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.665: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.716: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:16.735: 38977956333375: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.735: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.789: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:16.809: 38977956407047: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.809: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.860: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:16.878: 38977956476558: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.878: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.931: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:16.950: 38977956548460: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:16.950: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.005: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.030: 38977956627793: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.030: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.083: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.104: 38977956702295: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.104: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.158: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.177: 38977956775654: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.177: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.229: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.248: 38977956846260: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.248: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.300: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.320: 38977956918351: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.320: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.371: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.391: 38977956989270: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.391: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.443: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.463: 38977957060759: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.463: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.514: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.533: 38977957131550: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.533: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.587: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.606: 38977957204127: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.606: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.667: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.687: 38977957284862: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.687: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.739: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.761: 38977957359041: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.761: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.846: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.865: 38977957462805: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.865: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.918: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:17.938: 38977957535756: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.938: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:17.988: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:18.008: 38977957605957: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.008: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.079: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:18.114: 38977957712596: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.115: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.198: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:18.229: 38977957826918: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.229: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.319: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:18.350: 38977957947862: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.350: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.433: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:18.468: 38977958066376: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.468: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.553: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:18.584: 38977958182161: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.584: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.662: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:18.693: 38977958291731: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.694: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.775: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:18.811: 38977958409477: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.811: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.898: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:18.925: 38977958523372: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:18.925: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.018: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:19.049: 38977958647322: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.049: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.131: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:19.162: 38977958760221: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.162: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.240: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:19.267: 38977958865190: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.267: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.346: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:19.374: 38977958971827: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.374: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.454: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:19.486: 38977959084084: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.486: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.569: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:19.601: 38977959198792: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.601: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.687: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:19.718: 38977959316392: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.718: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.797: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:19.829: 38977959427687: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.830: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.912: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:19.943: 38977959541600: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:19.943: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.026: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:20.058: 38977959656028: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.058: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.141: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:20.168: 38977959766292: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.168: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.252: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:20.280: 38977959878133: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.280: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.349: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:20.369: 38977959967484: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.369: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.423: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:20.443: 38977960040841: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.443: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.494: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:20.515: 38977960112828: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.515: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.594: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:20.628: 38977960225891: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.628: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.733: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:20.773: 38977960371535: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.773: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.840: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:20.873: 38977960471480: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.873: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.960: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:20.997: 38977960594965: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:20.997: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.088: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:21.124: 38977960722162: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.124: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.220: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:21.248: 38977960845972: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.248: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.338: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:21.367: 38977960965619: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.368: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.458: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:21.491: 38977961089582: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.491: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.595: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:21.632: 38977961229851: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.632: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.713: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:21.746: 38977961343752: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.746: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.847: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:21.883: 38977961481661: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.884: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:21.977: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:22.005: 38977961603155: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.005: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.098: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:22.138: 38977961727976: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.138: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.221: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:22.258: 38977961855787: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.258: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.347: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:22.382: 38977961980217: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.382: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.460: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:22.493: 38977962091539: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.493: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.568: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:22.595: 38977962193281: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.595: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.673: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:22.701: 38977962298801: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.701: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.779: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:22.807: 38977962405088: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.807: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.881: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:22.912: 38977962510592: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.913: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:22.989: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:23.020: 38977962618413: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.020: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.099: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:23.122: 38977962720199: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.122: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.197: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:23.233: 38977962831042: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.233: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.343: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:23.372: 38977962970169: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.372: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.448: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:23.476: 38977963074320: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.476: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.560: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:23.595: 38977963192878: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.595: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.687: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:23.719: 38977963316933: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.719: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.798: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:23.833: 38977963431462: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.833: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.918: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:23.953: 38977963551345: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:23.953: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.043: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:24.080: 38977963678411: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.080: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.179: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:24.212: 38977963810166: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.212: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.307: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:24.343: 38977963941251: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.343: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.433: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:24.469: 38977964067497: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.469: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.571: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:24.608: 38977964205964: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.608: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.709: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:24.745: 38977964343532: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.745: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.832: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:24.861: 38977964458803: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.861: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.942: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:24.975: 38977964572936: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:24.975: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.053: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.085: 38977964683594: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.086: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.168: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.196: 38977964794150: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.196: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.276: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.296: 38977964894626: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.297: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.350: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.370: 38977964968378: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.370: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.425: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.445: 38977965043327: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.445: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.499: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.521: 38977965118957: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.521: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.576: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.599: 38977965197655: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.600: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.654: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.675: 38977965273709: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.676: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.747: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.776: 38977965374090: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.776: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.849: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.882: 38977965480041: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.882: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.965: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:25.994: 38977965592308: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:25.994: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.088: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:26.122: 38977965720534: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.122: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.212: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:26.245: 38977965842826: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.245: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.345: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:26.383: 38977965980996: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.383: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.482: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:26.520: 38977966117897: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.520: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.615: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:26.652: 38977966250694: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.653: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.740: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:26.772: 38977966370671: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.773: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.861: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:26.898: 38977966496238: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.898: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:26.982: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:27.016: 38977966613800: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.016: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.107: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:27.136: 38977966733918: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.136: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.224: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:27.260: 38977966858445: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.260: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.340: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:27.371: 38977966969142: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.371: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.457: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:27.496: 38977967094131: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.496: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.582: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:27.612: 38977967210615: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.613: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.699: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:27.734: 38977967331763: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.734: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.830: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:27.866: 38977967463786: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.866: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.955: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:27.985: 38977967583132: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:27.985: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.074: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:28.108: 38977967706232: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.108: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.185: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:28.224: 38977967821969: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.224: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.301: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:28.335: 38977967933425: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.335: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.417: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:28.458: 38977968056677: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.459: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.550: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:28.579: 38977968176992: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.579: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.686: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:28.751: 38977968349496: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.751: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:28.942: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:29.014: 38977968612115: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.014: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.133: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:29.161: 38977968759551: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.161: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.240: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:29.276: 38977968874517: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.276: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.356: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:29.385: 38977968983204: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.385: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.468: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:29.526: 38977969124503: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.526: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.610: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:29.642: 38977969240138: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.642: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.724: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:29.752: 38977969350144: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.752: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.835: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:29.868: 38977969465922: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.868: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.953: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:29.990: 38977969588053: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:29.990: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.075: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:30.108: 38977969706167: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.108: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.189: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:30.223: 38977969820905: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.223: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.304: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:30.340: 38977969938331: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.340: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.420: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:30.451: 38977970049441: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.451: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.534: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:30.567: 38977970164836: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.567: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.652: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:30.679: 38977970277661: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.680: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.757: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:30.784: 38977970382701: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.785: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.866: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:30.893: 38977970491701: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.894: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:30.978: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:31.006: 38977970604128: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.006: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.087: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:31.119: 38977970716965: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.119: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.201: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:31.234: 38977970831991: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.234: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.335: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:31.367: 38977970965471: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.367: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.458: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:31.495: 38977971093160: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.495: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.579: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:31.608: 38977971206586: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.609: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.688: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:31.717: 38977971314825: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.717: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.797: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:31.827: 38977971424925: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.827: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.910: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:31.941: 38977971538852: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:31.941: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.018: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:32.046: 38977971644515: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.046: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.139: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:32.172: 38977971770532: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.172: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.261: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:32.293: 38977971891420: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.293: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.395: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:32.431: 38977972029225: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.431: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.525: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:32.562: 38977972160078: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.562: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.648: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:32.679: 38977972276838: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.679: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.762: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:32.799: 38977972396792: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.799: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.882: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:32.910: 38977972508595: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.911: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:32.994: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:33.023: 38977972621172: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.023: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.105: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:33.142: 38977972740548: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.142: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.222: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:33.247: 38977972845255: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.247: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.330: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:33.363: 38977972961331: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.363: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.455: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:33.484: 38977973082716: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.485: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.572: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:33.606: 38977973203811: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.606: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.695: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:33.725: 38977973323282: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.725: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.810: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:33.846: 38977973444680: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.847: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.925: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:33.958: 38977973556245: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:33.958: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.058: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:34.098: 38977973696278: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.098: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.214: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:34.257: 38977973854837: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.257: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.374: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:34.403: 38977974001244: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.403: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.463: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:34.486: 38977974084389: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.486: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.545: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:34.567: 38977974165407: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.567: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.626: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:34.649: 38977974246845: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.649: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.709: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:34.731: 38977974329236: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.731: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.792: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:34.816: 38977974414155: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.816: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.876: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:34.898: 38977974496117: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.898: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.957: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:34.981: 38977974579418: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:34.981: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.041: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:35.076: 38977974673783: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.076: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.160: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:35.197: 38977974795720: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.198: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.278: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:35.316: 38977974914141: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.316: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.397: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:35.430: 38977975028396: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.430: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.519: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:35.548: 38977975146272: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.548: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.633: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:35.666: 38977975264033: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.666: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.768: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:35.794: 38977975391867: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.794: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.852: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:35.875: 38977975472842: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.875: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.943: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:35.972: 38977975570692: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:35.973: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.063: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:36.092: 38977975690201: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.092: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.176: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:36.209: 38977975807448: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.209: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.289: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:36.328: 38977975925784: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.328: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.419: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:36.448: 38977976046538: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.448: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.537: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:36.566: 38977976164242: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.566: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.655: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:36.689: 38977976286932: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.689: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.774: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:36.811: 38977976409587: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.811: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.892: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:36.925: 38977976523700: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:36.926: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.014: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:37.043: 38977976641653: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.044: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.127: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:37.159: 38977976757456: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.159: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.247: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:37.275: 38977976873283: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.275: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.362: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:37.395: 38977976992949: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.395: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.482: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:37.518: 38977977111985: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.518: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.601: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:37.637: 38977977235610: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.638: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.728: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:37.756: 38977977354366: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.756: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.833: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:37.869: 38977977467424: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.869: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.947: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:37.980: 38977977578042: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:37.980: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.066: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:38.099: 38977977696812: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.099: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.184: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:38.212: 38977977810318: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.212: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.295: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:38.327: 38977977925428: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.327: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.414: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:38.442: 38977978040223: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.442: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.525: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:38.553: 38977978150953: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.553: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.638: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:38.666: 38977978263733: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.666: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.744: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:38.776: 38977978374154: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.776: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.857: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:38.885: 38977978482779: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.885: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:38.971: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:39.004: 38977978601976: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.004: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.081: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:39.109: 38977978707526: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.109: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.195: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:39.224: 38977978821750: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.224: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.304: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:39.332: 38977978930562: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.332: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.415: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:39.443: 38977979041573: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.443: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.525: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:39.553: 38977979151054: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.553: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.635: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:39.667: 38977979265503: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.667: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.756: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:39.784: 38977979382121: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.784: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.866: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:39.898: 38977979496508: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.898: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.957: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:39.977: 38977979575417: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:39.977: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.030: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.050: 38977979648290: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.050: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.104: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.124: 38977979722252: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.124: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.177: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.197: 38977979795599: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.197: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.257: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.279: 38977979877019: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.279: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.349: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.381: 38977979979293: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.381: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.464: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.496: 38977980094079: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.496: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.571: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.593: 38977980190915: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.593: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.646: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.666: 38977980264090: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.666: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.720: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.740: 38977980338194: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.740: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.796: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.816: 38977980414688: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.817: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.869: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.888: 38977980486709: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.889: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.951: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:40.973: 38977980571319: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:40.973: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.042: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:41.067: 38977980664939: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.067: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.155: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:41.188: 38977980786513: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.188: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.284: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:41.321: 38977980919086: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.321: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.420: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:41.461: 38977981059326: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.461: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.558: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:41.595: 38977981192878: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.595: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.688: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:41.721: 38977981319261: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.721: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.830: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:41.857: 38977981454971: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.857: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.936: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:41.964: 38977981562583: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:41.964: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.048: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:42.076: 38977981674383: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.076: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.173: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:42.205: 38977981803119: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.205: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.306: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:42.338: 38977981936162: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.338: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.424: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:42.461: 38977982059033: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.461: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.543: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:42.579: 38977982176990: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.579: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.655: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:42.683: 38977982281514: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.683: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.769: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:42.797: 38977982395595: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.798: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.879: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:42.906: 38977982504617: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.907: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:42.991: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:43.019: 38977982617217: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.019: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.101: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:43.133: 38977982731114: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.133: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.214: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:43.245: 38977982843420: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.245: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.327: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:43.355: 38977982953051: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.355: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.436: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:43.472: 38977983069915: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.472: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.549: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:43.577: 38977983175050: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.577: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.662: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:43.691: 38977983289029: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.691: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.778: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:43.807: 38977983405168: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.807: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.891: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:43.916: 38977983514037: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.916: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:43.996: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:44.025: 38977983623259: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.025: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.112: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:44.141: 38977983739446: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.141: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.220: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:44.258: 38977983856419: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.258: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.343: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:44.378: 38977983976280: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.378: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.466: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:44.489: 38977984087663: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.490: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.564: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:44.592: 38977984190037: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.592: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.673: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:44.700: 38977984297778: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.700: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.775: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:44.811: 38977984409168: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.811: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.894: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:44.927: 38977984525178: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.927: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:44.987: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.006: 38977984604093: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.006: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.060: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.080: 38977984678228: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.080: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.134: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.153: 38977984751652: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.154: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.207: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.227: 38977984825717: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.228: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.283: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.304: 38977984902582: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.304: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.359: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.379: 38977984976836: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.379: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.432: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.453: 38977985050920: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.453: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.508: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.529: 38977985127178: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.529: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.586: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.608: 38977985205969: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.608: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.665: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.688: 38977985286712: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.689: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.746: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.767: 38977985365446: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.767: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.822: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.844: 38977985442358: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.844: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.899: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.919: 38977985517607: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.920: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.973: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:45.994: 38977985591896: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:45.994: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.048: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.068: 38977985666154: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.068: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.123: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.143: 38977985741185: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.143: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.196: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.217: 38977985814799: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.217: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.270: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.290: 38977985888205: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.290: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.344: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.364: 38977985962170: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.364: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.418: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.438: 38977986036391: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.438: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.493: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.513: 38977986111630: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.514: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.566: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.587: 38977986185081: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.587: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.643: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.663: 38977986261056: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.663: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.719: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.739: 38977986337204: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.739: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.800: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.821: 38977986418995: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.821: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.902: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:46.935: 38977986533593: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:46.935: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.024: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:47.054: 38977986651821: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.062: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.143: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:47.180: 38977986778707: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.181: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.261: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:47.295: 38977986893318: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.295: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.384: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:47.414: 38977987011980: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.414: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.503: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:47.533: 38977987130860: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.533: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.622: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:47.655: 38977987253564: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.655: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.746: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:47.775: 38977987373622: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.776: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.857: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:47.894: 38977987492295: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.894: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:47.979: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:48.009: 38977987607054: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.009: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.099: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:48.133: 38977987730801: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.133: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.214: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:48.249: 38977987847254: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.249: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.334: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:48.367: 38977987965380: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.367: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.452: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:48.481: 38977988079084: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.481: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.565: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:48.602: 38977988200641: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.603: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.683: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:48.716: 38977988314062: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.716: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.800: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:48.834: 38977988431760: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.834: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.918: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:48.951: 38977988549215: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:48.951: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.039: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:49.068: 38977988666726: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.069: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.153: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:49.182: 38977988779848: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.182: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.266: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:49.299: 38977988896894: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.299: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.380: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:49.413: 38977989011314: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.413: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.501: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:49.534: 38977989132230: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.534: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.617: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:49.648: 38977989246401: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.648: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.740: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:49.769: 38977989367332: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.769: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.863: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:49.892: 38977989490473: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.892: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.960: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:49.983: 38977989580862: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:49.983: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.045: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.066: 38977989664242: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.066: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.124: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.145: 38977989743304: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.145: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.222: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.257: 38977989855035: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.257: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.342: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.371: 38977989969157: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.371: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.433: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.456: 38977990053976: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.456: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.516: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.538: 38977990136435: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.538: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.601: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.623: 38977990221081: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.623: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.681: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.703: 38977990301396: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.703: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.762: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.785: 38977990382956: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.785: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.844: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.866: 38977990464338: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.866: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.925: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:50.947: 38977990545582: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:50.947: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.005: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:51.027: 38977990625486: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.027: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.086: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:51.108: 38977990706243: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.108: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.166: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:51.188: 38977990786177: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.188: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.249: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:51.271: 38977990869620: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.272: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.334: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:51.357: 38977990955540: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.357: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.418: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:51.440: 38977991038632: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.441: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.556: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:51.586: 38977991184207: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.586: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.670: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:51.693: 38977991291641: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.694: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.783: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:51.816: 38977991414188: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.816: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.910: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:51.943: 38977991541557: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:51.943: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.037: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:52.066: 38977991664091: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.066: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.159: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:52.190: 38977991788674: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.191: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.280: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:52.315: 38977991912928: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.315: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.400: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:52.440: 38977992037769: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.440: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.510: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:52.535: 38977992133705: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.536: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.596: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:52.619: 38977992217009: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.619: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.680: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:52.703: 38977992300909: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.703: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.762: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:52.784: 38977992382099: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.784: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.842: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:52.863: 38977992461687: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.864: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.923: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:52.946: 38977992544324: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:52.946: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.006: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.029: 38977992627066: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.029: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.092: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.113: 38977992711503: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.113: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.170: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.191: 38977992789702: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.192: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.250: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.272: 38977992870133: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.272: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.329: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.351: 38977992948893: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.351: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.407: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.428: 38977993026384: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.428: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.486: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.512: 38977993110407: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.512: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.572: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.595: 38977993193001: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.595: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.657: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.683: 38977993280919: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.683: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.744: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.766: 38977993363760: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.766: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.824: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.846: 38977993443801: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.846: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.905: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:53.926: 38977993524688: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.927: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:53.987: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.009: 38977993606954: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.009: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.068: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.090: 38977993687905: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.090: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.147: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.169: 38977993767052: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.169: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.225: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.249: 38977993847289: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.249: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.307: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.328: 38977993925901: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.328: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.384: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.405: 38977994003406: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.405: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.463: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.485: 38977994083030: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.485: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.538: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.558: 38977994156667: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.559: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.614: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.638: 38977994236322: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.638: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.697: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.717: 38977994314875: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.717: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.770: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.792: 38977994389766: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.792: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.845: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.866: 38977994464167: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.866: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.919: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:54.940: 38977994537857: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.940: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:54.994: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.014: 38977994612051: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.014: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.068: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.088: 38977994686565: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.088: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.143: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.163: 38977994761092: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.163: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.226: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.263: 38977994861089: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.263: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.319: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.340: 38977994938299: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.340: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.396: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.418: 38977995015748: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.418: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.474: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.495: 38977995092894: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.495: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.551: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.572: 38977995170381: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.572: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.628: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.649: 38977995247414: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.649: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.705: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.725: 38977995323511: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.725: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.818: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.847: 38977995445443: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.847: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.928: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:55.961: 38977995559527: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:55.961: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.050: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:56.079: 38977995677581: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.079: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.168: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:56.197: 38977995795571: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.197: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.286: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:56.323: 38977995921232: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.323: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.408: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:56.441: 38977996039635: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.442: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.525: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:56.559: 38977996156879: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.559: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.644: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:56.673: 38977996271678: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.674: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:56.770: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:57.840: 38977997438722: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:57.841: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:57.927: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:57.960: 38977997557981: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:57.960: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.040: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.060: 38977997658048: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.060: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.115: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.136: 38977997734085: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.136: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.214: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.243: 38977997841700: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.244: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.307: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.335: 38977997933511: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.335: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.418: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.450: 38977998048248: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.450: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.531: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.564: 38977998161998: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.564: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.635: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.655: 38977998253419: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.655: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.709: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.729: 38977998327652: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.730: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.786: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.807: 38977998405472: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.807: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.862: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.883: 38977998481110: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.883: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.938: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:58.959: 38977998556992: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:58.959: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.013: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:59.034: 38977998631931: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.034: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.105: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:59.134: 38977998732205: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.134: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.189: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:59.210: 38977998808318: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.210: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.269: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:59.290: 38977998888059: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.290: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.362: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:59.395: 38977998992920: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.395: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.476: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:59.504: 38977999102708: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.505: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.591: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:59.624: 38977999221835: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.624: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.716: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:59.749: 38977999347639: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.750: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.849: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:24:59.887: 38977999485714: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.888: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:24:59.984: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:00.025: 38977999623594: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.026: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.127: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:00.163: 38977999761208: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.163: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.250: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:00.282: 38977999880352: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.282: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.369: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:00.405: 38978000002868: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.405: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.506: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:00.550: 38978000148135: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.550: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.678: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:00.718: 38978000316130: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.718: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.829: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:00.868: 38978000466298: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:00.868: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.106: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:01.158: 38978000756117: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.158: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.290: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:01.326: 38978000924222: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.326: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.445: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:01.494: 38978001092125: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.494: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.622: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:01.657: 38978001255311: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.657: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.751: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:01.790: 38978001388351: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.790: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.893: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:01.926: 38978001524157: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:01.926: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.026: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:02.066: 38978001663972: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.066: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.171: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:02.218: 38978001815978: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.218: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.339: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:02.385: 38978001983000: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.385: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.499: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:02.547: 38978002145552: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.547: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.674: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:02.722: 38978002320223: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.722: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.838: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:02.870: 38978002468312: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.870: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.962: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:02.998: 38978002596634: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:02.999: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.087: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:03.123: 38978002721527: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.123: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.209: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:03.252: 38978002850104: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.252: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.325: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:03.348: 38978002946071: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.348: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.416: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:03.439: 38978003037303: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.439: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.509: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:03.532: 38978003130016: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.532: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.594: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:03.616: 38978003214442: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.616: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.676: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:03.698: 38978003296401: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.698: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.758: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:03.780: 38978003377969: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.780: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.838: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:03.860: 38978003458297: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.860: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.917: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:03.938: 38978003536226: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:03.938: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.054: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:04.108: 38978003706277: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.108: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.243: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:04.279: 38978003877076: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.279: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.375: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:04.415: 38978004013505: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.415: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.500: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:04.536: 38978004134458: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.536: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.627: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:04.656: 38978004253733: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.656: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.761: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:04.797: 38978004395456: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.797: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.881: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:04.918: 38978004516130: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.918: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:04.998: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:05.034: 38978004632462: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.034: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.114: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:05.147: 38978004745104: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.147: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.231: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:05.264: 38978004862627: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.265: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.357: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:05.392: 38978004990558: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.392: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.485: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:05.514: 38978005111831: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.518: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.597: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:05.629: 38978005227148: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.629: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.713: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:05.746: 38978005343792: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.746: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.839: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:05.867: 38978005465433: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.867: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.946: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:05.979: 38978005577418: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:05.979: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.062: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:06.090: 38978005688578: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.090: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.175: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:06.203: 38978005801602: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.204: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.285: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:06.321: 38978005919268: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.321: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.398: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:06.426: 38978006024089: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.426: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.508: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:06.537: 38978006135089: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.537: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.621: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:06.659: 38978006256877: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.659: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.744: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:06.789: 38978006387105: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.789: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.892: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:06.924: 38978006521946: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:06.924: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.001: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:07.037: 38978006634981: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.037: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.115: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:07.144: 38978006742024: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.144: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.231: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:07.259: 38978006856943: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.259: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.342: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:07.370: 38978006968293: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.370: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.456: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:07.484: 38978007082274: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.484: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.566: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:07.599: 38978007196890: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.599: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.677: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:07.709: 38978007307681: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.710: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.792: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:07.821: 38978007418808: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.821: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.903: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:07.935: 38978007533679: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:07.936: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.022: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:08.047: 38978007645502: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.047: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.122: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:08.155: 38978007752869: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.155: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.280: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:08.309: 38978007907187: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.309: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.362: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:08.382: 38978007980545: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.382: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.462: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:08.489: 38978008087564: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.489: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.573: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:08.601: 38978008198906: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.601: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.681: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:08.708: 38978008306060: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.708: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.787: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:08.815: 38978008412899: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.815: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.891: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:08.922: 38978008520221: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.922: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:08.998: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:09.025: 38978008623012: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.025: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.107: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:09.131: 38978008729028: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.131: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.206: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:09.233: 38978008830983: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.233: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.310: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:09.337: 38978008935402: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.337: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.416: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:09.447: 38978009044787: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.447: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.521: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:09.558: 38978009156586: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.558: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.635: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:09.663: 38978009260742: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.663: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.748: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:09.776: 38978009374141: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.776: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.853: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:09.884: 38978009482629: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.885: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.965: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:09.993: 38978009591235: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:09.993: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.078: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:10.101: 38978009699704: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.102: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.182: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:10.209: 38978009807704: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.210: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.286: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:10.320: 38978009917896: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.320: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.397: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:10.430: 38978010027821: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.430: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.511: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:10.540: 38978010138154: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.540: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.623: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:10.659: 38978010257610: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.659: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.739: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:10.768: 38978010365798: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.768: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.851: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:10.888: 38978010486460: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.888: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:10.972: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:11.006: 38978010603874: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.010: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.100: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:11.133: 38978010731642: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.134: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.213: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:11.250: 38978010848428: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.250: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.331: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:11.363: 38978010961650: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.364: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.449: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:11.483: 38978011081192: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.483: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.571: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:11.601: 38978011199128: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.601: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.692: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:11.722: 38978011320549: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.722: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.810: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:11.845: 38978011443486: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.845: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.932: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:11.963: 38978011561213: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:11.963: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.052: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:12.090: 38978011687951: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.090: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.175: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:12.205: 38978011802921: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.205: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.289: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:12.323: 38978011921014: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.323: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.409: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:12.443: 38978012040894: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.443: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.528: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:12.562: 38978012160057: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.562: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.649: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:12.680: 38978012278058: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.680: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.767: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:12.802: 38978012400166: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.802: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.887: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:12.926: 38978012524087: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:12.926: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.011: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:13.048: 38978012646353: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.048: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.133: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:13.164: 38978012761964: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.164: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.251: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:13.282: 38978012879763: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.282: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.369: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:13.403: 38978013001116: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.403: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.488: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:13.523: 38978013120861: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.523: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.609: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:13.644: 38978013241885: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.644: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.729: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:13.762: 38978013360195: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.762: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.847: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:13.877: 38978013474950: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.877: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:13.970: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:14.004: 38978013602083: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.004: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.093: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:14.122: 38978013720556: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.122: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.207: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:14.241: 38978013838938: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.241: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.326: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:14.359: 38978013957565: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.359: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.445: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:14.478: 38978014076536: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.478: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.564: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:14.593: 38978014191185: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.593: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.679: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:14.712: 38978014310160: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.712: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.797: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:14.826: 38978014424322: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.826: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.911: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:14.944: 38978014542579: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:14.944: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.029: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:15.059: 38978014656777: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.059: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.146: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:15.175: 38978014773258: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.175: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.261: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:15.294: 38978014892691: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.295: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.383: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:15.412: 38978015009981: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.412: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.496: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:15.525: 38978015123003: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.525: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.613: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:15.642: 38978015240236: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.642: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.725: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:15.754: 38978015352345: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.754: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.841: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:15.880: 38978015477747: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.880: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:15.971: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:16.002: 38978015599728: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.002: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.092: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:16.121: 38978015719487: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.121: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.210: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:16.232: 38978015830148: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.232: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.290: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:16.313: 38978015910956: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.313: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.400: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:16.431: 38978016028782: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.431: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.516: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:16.546: 38978016144052: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.546: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.643: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:16.687: 38978016285288: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.687: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.770: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:16.791: 38978016389250: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.791: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.858: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:16.887: 38978016485505: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.887: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:16.971: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:17.005: 38978016603208: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.005: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.089: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:17.122: 38978016720708: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.123: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.205: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:17.238: 38978016836220: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.238: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.322: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:17.342: 38978016940318: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.342: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.425: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:17.458: 38978017055780: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.458: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.540: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:17.569: 38978017166968: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.569: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.686: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:17.730: 38978017328265: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.730: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.799: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:17.835: 38978017432908: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.835: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.910: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:17.943: 38978017541453: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:17.943: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.023: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:18.052: 38978017650366: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.052: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.139: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:18.168: 38978017766170: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.168: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.251: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:18.285: 38978017883020: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.285: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.363: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:18.390: 38978017988429: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.390: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.465: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:18.501: 38978018099515: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.501: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.591: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:18.620: 38978018217739: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.620: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.698: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:18.727: 38978018325026: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.727: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.810: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:18.837: 38978018435252: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.837: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.920: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:18.951: 38978018549607: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:18.951: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.028: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:19.064: 38978018662069: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.064: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.143: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:19.171: 38978018768897: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.171: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.255: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:19.279: 38978018877004: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.279: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.360: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:19.388: 38978018985823: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.388: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.465: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:19.498: 38978019095948: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.498: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.581: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:19.609: 38978019207449: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.609: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.692: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:19.721: 38978019318942: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.721: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.775: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:19.796: 38978019394570: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.796: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.850: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:19.869: 38978019467290: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.869: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.921: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:19.940: 38978019537998: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.940: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:19.992: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.011: 38978019609021: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.011: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.063: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.082: 38978019680208: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.082: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.146: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.165: 38978019763645: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.166: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.217: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.236: 38978019834538: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.236: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.295: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.314: 38978019912713: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.315: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.365: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.384: 38978019982445: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.384: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.443: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.461: 38978020059511: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.461: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.509: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.527: 38978020124980: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.527: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.577: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.595: 38978020193459: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.595: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.646: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.665: 38978020262825: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.665: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.715: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.734: 38978020332381: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.734: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.790: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.813: 38978020411588: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.814: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.865: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.884: 38978020482683: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.885: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.936: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:20.954: 38978020552126: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:20.954: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:21.004: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:21.022: 38978020620160: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:21.022: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:21.071: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:21.090: 38978020687977: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:21.090: write 23 regs
(process:17718): libfprint-aeslib-DEBUG: 04:25:21.139: all registers written
(process:17718): libfprint-aes2501-DEBUG: 04:25:21.159: 38978020757024: ../libfprint/drivers/aes2501.c:310
(process:17718): libfprint-aeslib-DEBUG: 04:25:21.159: write 23 regs
** (umockdev-run:17711): DEBUG: 04:25:21.210: umockdev-utils.vala:50: umockdev: caught signal 15, propagating to child
** (umockdev-run:17711): DEBUG: 04:25:21.218: umockdev.vala:150: Removing test bed /tmp/umockdev.WZC6A2
(umockdev-run:17711): GLib-DEBUG: 04:25:21.266: unsetenv() is not thread-safe and should not be used after threads are created
==============================================================================
================================== 109/116 ===================================
test: libfprint:unit-tests / fpi-ssm
start time: 04:25:21
duration: 1.16s
result: exit status 0
command: LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint:/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=64 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm
----------------------------------- stdout -----------------------------------
# random seed: R02S285d1f8f7a687eb50c6fe2a81f085efd
1..42
# Start of ssm tests
ok 1 /ssm/new
ok 2 /ssm/set_data
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.319: [fake_test_dev] FPI_TEST_SSM entering state 0
ok 3 /ssm/start
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.320: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.320: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 4 /ssm/next
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.320: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.320: [fake_test_dev] FPI_TEST_SSM entering state 2
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.320: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 5 /ssm/jump_to_state
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.321: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.321: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 6 /ssm/mark_completed
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.321: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.321: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.322: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
ok 7 /ssm/mark_failed
# Start of new tests
ok 8 /ssm/new/full
ok 9 /ssm/new/no_handler
ok 10 /ssm/new/wrong_states
# End of new tests
# Start of set_data tests
ok 11 /ssm/set_data/cleanup
# End of set_data tests
# Start of start tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.331: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.331: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully
ok 12 /ssm/start/single
# End of start tests
# Start of next tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.332: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.332: [fake_test_dev] FPI_TEST_SSM entering state 1
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.332: [fake_test_dev] FPI_TEST_SSM entering state 2
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.332: [fake_test_dev] FPI_TEST_SSM entering state 3
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.332: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 13 /ssm/next/complete
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.333: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 14 /ssm/next/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.333: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.334: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 15 /ssm/next/with_delayed
# End of next tests
# Start of jump_to_state tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.436: [fake_test_dev] FPI_TEST_SSM entering state 2
ok 16 /ssm/jump_to_state/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.436: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.436: [fake_test_dev] FPI_TEST_SSM entering state 2
ok 17 /ssm/jump_to_state/with_delayed
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.537: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.537: [fake_test_dev] FPI_TEST_SSM entering state 3
ok 18 /ssm/jump_to_state/last
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.538: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.538: [fake_test_dev] FPI_TEST_SSM entering state 14
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.538: [fake_test_dev] FPI_TEST_SSM entering state -10
ok 19 /ssm/jump_to_state/wrong
# End of jump_to_state tests
# Start of mark_completed tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.539: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 20 /ssm/mark_completed/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.539: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.539: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 21 /ssm/mark_completed/with_delayed
# End of mark_completed tests
# Start of mark_failed tests
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.642: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.642: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
ok 22 /ssm/mark_failed/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.643: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.643: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.643: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
ok 23 /ssm/mark_failed/with_delayed
# End of mark_failed tests
# Start of delayed tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.746: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.758: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 24 /ssm/delayed/next
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.758: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.770: [fake_test_dev] FPI_TEST_SSM entering state 2
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.782: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 25 /ssm/delayed/jump_to_state
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.782: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.794: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 26 /ssm/delayed/mark_completed
# Start of next tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.794: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.795: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 27 /ssm/delayed/next/cancel
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.910: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 28 /ssm/delayed/next/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.910: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.922: [fake_test_dev] FPI_TEST_SSM entering state 1
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.934: [fake_test_dev] FPI_TEST_SSM entering state 2
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.946: [fake_test_dev] FPI_TEST_SSM entering state 3
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.958: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 29 /ssm/delayed/next/complete
# End of next tests
# Start of jump_to_state tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.960: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:21.961: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 30 /ssm/delayed/jump_to_state/cancel
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.074: [fake_test_dev] FPI_TEST_SSM entering state 2
ok 31 /ssm/delayed/jump_to_state/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.076: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.086: [fake_test_dev] FPI_TEST_SSM entering state 3
ok 32 /ssm/delayed/jump_to_state/last
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.088: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.098: [fake_test_dev] FPI_TEST_SSM entering state 14
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.109: [fake_test_dev] FPI_TEST_SSM entering state -10
ok 33 /ssm/delayed/jump_to_state/wrong
# End of jump_to_state tests
# Start of mark_completed tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.110: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.110: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 34 /ssm/delayed/mark_completed/cancel
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.226: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 35 /ssm/delayed/mark_completed/not_started
# End of mark_completed tests
# Start of cancel tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.318: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.318: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.319: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 36 /ssm/delayed/cancel/error
# End of cancel tests
# End of delayed tests
# Start of subssm tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.319: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.319: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.319: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.320: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.320: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 37 /ssm/subssm/start
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.320: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.320: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later.
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.320: [fake_test_dev] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later.
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later.
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.321: [fake_test_dev] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later.
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later.
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.321: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later.
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later.
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.321: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later.
ok 38 /ssm/subssm/mark_failed
# Start of start tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.321: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.322: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.322: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.322: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.322: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 39 /ssm/subssm/start/with_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.322: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.323: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.424: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.424: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 40 /ssm/subssm/start/with_delayed
# End of start tests
# End of subssm tests
# Start of cleanup tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.425: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.425: [fake_test_dev] FPI_TEST_SSM entering state 2
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.425: [fake_test_dev] FPI_TEST_SSM entering state 3
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.425: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 41 /ssm/cleanup/complete
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.425: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.426: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.426: [fake_test_dev] FPI_TEST_SSM entering state 2
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.426: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.426: [fake_test_dev] FPI_TEST_SSM entering state 3
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.426: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-ssm:17996): libfprint-SSM-DEBUG: 04:25:22.427: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup
ok 42 /ssm/cleanup/fail
# End of cleanup tests
# End of ssm tests
==============================================================================
================================== 110/116 ===================================
test: libfprint:unit-tests / fpi-assembling
start time: 04:25:22
duration: 0.85s
result: exit status 0
command: LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint:/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints MALLOC_PERTURB_=169 UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-assembling
----------------------------------- stdout -----------------------------------
# random seed: R02S92606a8e5f92da5dd52b32004e8d026a
1..1
# Start of assembling tests
# libfprint-assembling-DEBUG: calc delta completed in 0.264187 secs
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-assembling:17998): libfprint-assembling-DEBUG: 04:25:22.756: calc delta completed in 0.264187 secs
# libfprint-assembling-DEBUG: calc delta completed in 0.248018 secs
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-assembling:17998): libfprint-assembling-DEBUG: 04:25:23.005: calc delta completed in 0.248018 secs
# libfprint-assembling-DEBUG: errors: 0 rev: 130848
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-assembling:17998): libfprint-assembling-DEBUG: 04:25:23.005: errors: 0 rev: 130848
# libfprint-assembling-DEBUG: calc delta completed in 0.277528 secs
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-assembling:17998): libfprint-assembling-DEBUG: 04:25:23.283: calc delta completed in 0.277528 secs
# libfprint-assembling-DEBUG: height is 310
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-assembling:17998): libfprint-assembling-DEBUG: 04:25:23.284: height is 310
ok 1 /assembling/frames
# End of assembling tests
==============================================================================
================================== 111/116 ===================================
test: libfprint:unit-tests / fp-context
start time: 04:25:23
duration: 1.64s
result: exit status 0
command: LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint:/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint MALLOC_PERTURB_=71 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context
----------------------------------- stdout -----------------------------------
# random seed: R02S3a739f85a24ec506c6d368a13ff7009e
1..9
# Start of context tests
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.323: Initializing FpContext (libfprint version 1.94.6)
ok 1 /context/new
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.355: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.381: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.382: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.382: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.383: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.384: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.385: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.386: No driver found for USB device 1D6B:0002
ok 2 /context/no-devices
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:23.411: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.411: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.451: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.452: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.453: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.453: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.454: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.455: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.456: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0Q29A2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.457: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0Q29A2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.459: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.484: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.485: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.486: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:23.487: unsetenv() is not thread-safe and should not be used after threads are created
ok 3 /context/has-virtual-device
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.500: Initializing FpContext (libfprint version 1.94.6)
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:23.537: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.546: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.547: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.548: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.549: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.550: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.551: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.552: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-QKJNB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.553: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-QKJNB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.554: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.582: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.584: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.585: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:23.586: unsetenv() is not thread-safe and should not be used after threads are created
ok 4 /context/enumerates-new-devices
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:23.600: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.601: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.639: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.639: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.639: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.639: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.640: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.640: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.640: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-KG6LB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.640: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-KG6LB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.641: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.665: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.665: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.665: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:23.667: unsetenv() is not thread-safe and should not be used after threads are created
ok 5 /context/remove-device-closed
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:23.681: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.681: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.739: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.739: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.739: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.739: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.740: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.740: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.740: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-7PRQB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.740: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-7PRQB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:23.741: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.760: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.761: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.761: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_image-DEBUG: 04:25:23.762: 38978023360120: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_device_connection-DEBUG: 04:25:23.790: 38978023388185: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:23.894: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.894: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.895: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:23.895: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_image-DEBUG: 04:25:23.896: 38978023493791: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.006: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.006: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.007: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.007: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:24.008: unsetenv() is not thread-safe and should not be used after threads are created
ok 6 /context/remove-device-closing
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:24.027: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.027: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.099: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.099: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.100: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.100: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.114: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.114: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.115: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-2SOCB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.115: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-2SOCB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.116: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.134: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.134: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.135: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_image-DEBUG: 04:25:24.135: 38978023733561: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_device_connection-DEBUG: 04:25:24.136: 38978023733867: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.238: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.238: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.239: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.239: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_image-DEBUG: 04:25:24.240: 38978023838217: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.342: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.342: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.343: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.343: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:24.344: unsetenv() is not thread-safe and should not be used after threads are created
ok 7 /context/remove-device-open
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:24.348: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.348: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.382: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.383: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.383: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.383: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.383: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.384: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.384: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-E1S5A2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.384: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-E1S5A2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.385: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.406: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.406: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.407: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_image-DEBUG: 04:25:24.407: 38978024005513: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_device_connection-DEBUG: 04:25:24.408: 38978024005772: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.510: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.510: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.511: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.511: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_image-DEBUG: 04:25:24.512: 38978024110036: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.614: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.614: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.615: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.615: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:24.616: unsetenv() is not thread-safe and should not be used after threads are created
ok 8 /context/remove-device-opening
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:24.628: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.629: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.663: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.663: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.664: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.665: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.670: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.670: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.671: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-F54MB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.671: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-F54MB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-context-DEBUG: 04:25:24.672: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.691: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.691: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.692: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_image-DEBUG: 04:25:24.693: 38978024290807: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_device_connection-DEBUG: 04:25:24.693: 38978024291114: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.798: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.798: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.799: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.799: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.801: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-image_device-DEBUG: Activating image device
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.802: Activating image device
# libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.802: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
# libfprint-image_device-DEBUG: Image device activation completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.802: Image device activation completed
# libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
# libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
# libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED
# libfprint-image_device-DEBUG: Deactivating image device
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.804: Deactivating image device
# libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.804: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
# libfprint-image_device-DEBUG: Image device deactivation completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.804: Image device deactivation completed
# libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.804: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
# libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.805: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL
# libfprint-device-DEBUG: Device reported enroll completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.805: Device reported enroll completion
# libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.805: Device reported finger status change: FP_FINGER_STATUS_NONE
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.806: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.806: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-virtual_image-DEBUG: 04:25:24.807: 38978024405443: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-image_device-DEBUG: 04:25:24.910: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.910: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.911: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): libfprint-device-DEBUG: 04:25:24.911: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-context:18000): GLib-DEBUG: 04:25:24.912: unsetenv() is not thread-safe and should not be used after threads are created
ok 9 /context/remove-device-active
# End of context tests
==============================================================================
================================== 112/116 ===================================
test: libfprint:drivers / elanspi
start time: 04:24:12
duration: 75.10s
result: killed by signal 15 SIGTERM
command: MALLOC_PERTURB_=70 G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 FP_DRIVERS_WHITELIST=elanspi MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/elanspi
----------------------------------- stdout -----------------------------------
** (umockdev-run:17773): DEBUG: 04:24:12.583: umockdev.vala:123: Created udev test bed /tmp/umockdev.XOSOB2
** (umockdev-run:17773): DEBUG: 04:24:12.584: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001/hidraw/hidraw0
** (umockdev-run:17773): DEBUG: 04:24:12.586: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001/hidraw/hidraw0 (subsystem hidraw)
** (umockdev-run:17773): DEBUG: 04:24:12.593: umockdev.vala:1430: create_node_for_device: creating pty device /tmp/umockdev.XOSOB2/dev/hidraw0: got pty /dev/pts/5
** (umockdev-run:17773): DEBUG: 04:24:12.593: umockdev.vala:1451: create_node_for_device: creating ptymap symlink /tmp/umockdev.XOSOB2/dev/.ptymap/_dev_pts_5
** (umockdev-run:17773): DEBUG: 04:24:12.594: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001
** (umockdev-run:17773): DEBUG: 04:24:12.597: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 (subsystem hid)
** (umockdev-run:17773): DEBUG: 04:24:12.605: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00
** (umockdev-run:17773): DEBUG: 04:24:12.611: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 (subsystem i2c)
** (umockdev-run:17773): DEBUG: 04:24:12.621: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1
** (umockdev-run:17773): DEBUG: 04:24:12.623: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 (subsystem i2c)
** (umockdev-run:17773): DEBUG: 04:24:12.626: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1
** (umockdev-run:17773): DEBUG: 04:24:12.628: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1 (subsystem platform)
** (umockdev-run:17773): DEBUG: 04:24:12.648: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1
** (umockdev-run:17773): DEBUG: 04:24:12.652: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1 (subsystem pci)
** (umockdev-run:17773): DEBUG: 04:24:12.678: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0
** (umockdev-run:17773): DEBUG: 04:24:12.680: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 (subsystem spidev)
** (umockdev-run:17773): DEBUG: 04:24:12.698: umockdev.vala:1430: create_node_for_device: creating pty device /tmp/umockdev.XOSOB2/dev/spidev0.0: got pty /dev/pts/6
** (umockdev-run:17773): DEBUG: 04:24:12.698: umockdev.vala:1451: create_node_for_device: creating ptymap symlink /tmp/umockdev.XOSOB2/dev/.ptymap/_dev_pts_6
** (umockdev-run:17773): DEBUG: 04:24:12.699: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00
** (umockdev-run:17773): DEBUG: 04:24:12.704: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 (subsystem spi)
** (umockdev-run:17773): DEBUG: 04:24:12.748: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0
** (umockdev-run:17773): DEBUG: 04:24:12.752: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 (subsystem spi_master)
** (umockdev-run:17773): DEBUG: 04:24:12.769: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3
** (umockdev-run:17773): DEBUG: 04:24:12.771: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 (subsystem platform)
** (umockdev-run:17773): DEBUG: 04:24:12.785: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2
** (umockdev-run:17773): DEBUG: 04:24:12.789: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2 (subsystem pci)
(umockdev-run:17773): GLib-GIO-DEBUG: 04:24:12.821: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
(umockdev-run:17773): GLib-DEBUG: 04:24:13.222: pidfd_open(17785) failed with error: Function not implemented
(process:17785): libfprint-context-DEBUG: 04:24:13.654: Initializing FpContext (libfprint version 1.94.6)
(process:17785): libfprint-device-DEBUG: 04:24:13.702: Device reported probe completion
(process:17785): libfprint-device-DEBUG: 04:24:13.703: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17785): libfprint-device-DEBUG: 04:24:13.703: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.719: 38977953317145: ../libfprint/drivers/elanspi.c:1562
(process:17785): libfprint-image_device-DEBUG: 04:24:13.724: Image device open completed
(process:17785): libfprint-device-DEBUG: 04:24:13.724: Device reported open completion
(process:17785): libfprint-device-DEBUG: 04:24:13.725: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17785): libfprint-device-DEBUG: 04:24:13.725: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17785): libfprint-device-DEBUG: 04:24:13.727: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17785): libfprint-image_device-DEBUG: 04:24:13.728: Activating image device
(process:17785): libfprint-image_device-DEBUG: 04:24:13.728: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17785): libfprint-SSM-DEBUG: 04:24:13.729: [elanspi] ELANSPI_INIT_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:13.754: [elanspi] ELANSPI_INIT_NSTATES entering state 1
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.754: <init> got status 81
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.754: <init> sync hw reset
(process:17785): libfprint-SSM-DEBUG: 04:24:13.762: [elanspi] ELANSPI_INIT_NSTATES entering state 2
(process:17785): libfprint-SSM-DEBUG: 04:24:13.770: [elanspi] ELANSPI_INIT_NSTATES entering state 3
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.770: <init> sw reset ok
(process:17785): libfprint-SSM-DEBUG: 04:24:13.778: [elanspi] ELANSPI_INIT_NSTATES entering state 4
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.778: <init> raw height = 96
(process:17785): libfprint-SSM-DEBUG: 04:24:13.784: [elanspi] ELANSPI_INIT_NSTATES entering state 5
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.784: <init> raw width = 96
(process:17785): libfprint-SSM-DEBUG: 04:24:13.796: [elanspi] ELANSPI_INIT_NSTATES entering state 6
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.796: <init> raw reg17 = 175
(process:17785): libfprint-SSM-DEBUG: 04:24:13.808: [elanspi] ELANSPI_INIT_NSTATES entering state 7
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.808: <init> raw version = 09
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.808: <init/detect> after hardcoded lookup; 96x96, version 1
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.808: <init/detect> found sensor ID 6 => [eFSA96SA] (96 x 96)
(process:17785): libfprint-SSM-DEBUG: 04:24:13.822: [elanspi] ELANSPI_INIT_NSTATES entering state 8
(process:17785): libfprint-SSM-DEBUG: 04:24:13.830: [elanspi] ELANSPI_INIT_NSTATES entering state 9
(process:17785): libfprint-device-DEBUG: 04:24:13.830: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17785): libfprint-SSM-DEBUG: 04:24:13.836: [elanspi] ELANSPI_INIT_NSTATES entering state 10
(process:17785): libfprint-SSM-DEBUG: 04:24:13.841: [elanspi] ELANSPI_INIT_NSTATES entering state 11
(process:17785): libfprint-SSM-DEBUG: 04:24:13.851: [elanspi] ELANSPI_INIT_NSTATES entering state 12
(process:17785): libfprint-SSM-DEBUG: 04:24:13.865: [elanspi] ELANSPI_INIT_NSTATES entering state 13
(process:17785): libfprint-SSM-DEBUG: 04:24:13.873: [elanspi] ELANSPI_INIT_NSTATES entering state 14
(process:17785): libfprint-SSM-DEBUG: 04:24:13.873: [elanspi] ELANSPI_INIT_NSTATES entering state 17
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.873: <init/otp> got vcm mode = 2
(process:17785): libfprint-SSM-DEBUG: 04:24:13.883: [elanspi] ELANSPI_INIT_NSTATES entering state 18
(process:17785): libfprint-SSM-DEBUG: 04:24:13.892: [elanspi] ELANSPI_INIT_NSTATES entering state 19
(process:17785): libfprint-elanspi-DEBUG: 04:24:13.892: <init/calibrate> starting calibrate
(process:17785): libfprint-SSM-DEBUG: 04:24:13.893: [elanspi] old calibrate entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:13.912: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:13.916: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:13.916: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:13.925: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:13.925: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:13.942: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:13.942: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:13.950: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:13.950: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:13.958: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:13.958: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:13.970: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:13.970: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:13.982: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:13.982: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:13.986: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:13.987: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.000: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.000: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.005: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.005: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.021: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.021: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.026: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.026: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.031: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.031: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.037: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.037: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.042: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.042: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.047: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.047: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.052: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.052: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.060: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.060: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.065: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.065: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.070: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.070: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.075: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.075: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.080: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.080: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.085: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.085: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.090: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.090: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:14.095: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:14.095: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:14.095: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:15.395: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-elanspi-DEBUG: 04:24:15.395: <calibold> dac init is 0x29
(process:17785): libfprint-SSM-DEBUG: 04:24:15.401: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:17.141: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:17.155: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:19.664: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-elanspi-DEBUG: 04:24:19.664: <calibold> calibration ok, saving bg image
(process:17785): libfprint-SSM-DEBUG: 04:24:19.670: [elanspi] old calibrate completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:19.670: [elanspi] ELANSPI_INIT_NSTATES entering state 20
(process:17785): libfprint-SSM-DEBUG: 04:24:19.670: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:21.840: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:21.840: [elanspi] ELANSPI_INIT_NSTATES entering state 21
(process:17785): libfprint-SSM-DEBUG: 04:24:21.841: [elanspi] ELANSPI_INIT_NSTATES completed successfully
(process:17785): libfprint-elanspi-DEBUG: 04:24:21.841: 38977961438889: ../libfprint/drivers/elanspi.c:1596
(process:17785): libfprint-image_device-DEBUG: 04:24:21.841: Image device activation completed
(process:17785): libfprint-image_device-DEBUG: 04:24:21.841: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17785): libfprint-image_device-DEBUG: 04:24:21.841: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17785): libfprint-SSM-DEBUG: 04:24:21.841: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:21.841: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:21.841: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-elanspi-DEBUG: 04:24:21.842: <change_state> started capturer
(process:17785): libfprint-device-DEBUG: 04:24:21.842: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17785): libfprint-SSM-DEBUG: 04:24:24.378: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:24.378: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:24.502: <guess> stddev=933d, ip=40, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:24.511: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:24.511: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:27.094: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:27.095: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:27.211: <guess> stddev=829d, ip=48, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:27.211: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:27.212: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:29.185: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:29.185: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:29.314: <guess> stddev=1307d, ip=37, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:29.314: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:29.314: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:31.043: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:31.044: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:31.116: <guess> stddev=1163d, ip=38, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:31.117: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:31.117: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:33.132: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:33.132: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:33.243: <guess> stddev=960d, ip=43, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:33.243: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:33.243: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:35.233: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:35.233: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:35.332: <guess> stddev=879d, ip=41, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:35.332: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:35.332: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:37.060: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:37.060: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:37.133: <guess> stddev=925d, ip=44, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:37.133: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:37.134: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:38.661: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:38.661: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:38.761: <guess> stddev=1244d, ip=37, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:38.761: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:38.761: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:41.022: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:41.022: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:41.129: <guess> stddev=709d, ip=48, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:41.130: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:41.130: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:43.175: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:43.175: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:43.276: <guess> stddev=553d, ip=54, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:43.277: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:43.277: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:45.159: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:45.159: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:45.234: <guess> stddev=904d, ip=44, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:45.234: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:45.235: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:46.640: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:46.640: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:46.714: <guess> stddev=951d, ip=46, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:46.714: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:46.714: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:48.016: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:48.016: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:48.088: <guess> stddev=795d, ip=44, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:48.089: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:48.089: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:49.574: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:49.574: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:49.676: <guess> stddev=985d, ip=41, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:49.677: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:49.677: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:51.754: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:51.754: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:51.829: <guess> stddev=938d, ip=40, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:51.830: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:51.830: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:53.994: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:53.994: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:54.128: <guess> stddev=846d, ip=40, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:54.128: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:54.128: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:56.625: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:56.626: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:56.697: <guess> stddev=693d, ip=56, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:56.697: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:56.698: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:24:58.880: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:24:58.880: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:24:58.952: <guess> stddev=777d, ip=50, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:24:58.952: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:24:58.953: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:01.070: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:01.070: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:25:01.172: <guess> stddev=824d, ip=45, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:25:01.172: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:25:01.172: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:03.746: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:03.746: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:25:03.853: <guess> stddev=521d, ip=50, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:25:03.854: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:25:03.858: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:06.118: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:06.118: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:25:06.223: <guess> stddev=670d, ip=47, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:25:06.224: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:25:06.224: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:07.973: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:07.973: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:25:08.063: <guess> stddev=1262d, ip=39, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:25:08.063: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:25:08.063: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:10.318: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:10.318: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:25:10.392: <guess> stddev=912d, ip=42, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:25:10.393: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:25:10.393: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:12.321: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:12.321: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:25:12.396: <guess> stddev=1402d, ip=37, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:25:12.397: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:25:12.397: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:14.332: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:14.332: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:25:14.416: <guess> stddev=1530d, ip=32, is_fp=0, is_empty=2
(process:17785): libfprint-SSM-DEBUG: 04:25:14.416: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:25:14.416: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:16.298: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:16.298: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:25:16.402: <guess> stddev=718159d, ip=6, is_fp=1, is_empty=0
(process:17785): libfprint-SSM-DEBUG: 04:25:16.402: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1
(process:17785): libfprint-SSM-DEBUG: 04:25:16.402: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:18.866: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:18.866: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2
(process:17785): libfprint-elanspi-DEBUG: 04:25:18.965: <guess> stddev=400929d, ip=0, is_fp=2, is_empty=0
(process:17785): libfprint-device-DEBUG: 04:25:18.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(process:17785): libfprint-image_device-DEBUG: 04:25:18.970: Image device reported finger status: on
(process:17785): libfprint-image_device-DEBUG: 04:25:18.971: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
(process:17785): libfprint-SSM-DEBUG: 04:25:18.971: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3
(process:17785): libfprint-SSM-DEBUG: 04:25:18.971: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:21.340: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:21.340: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4
(process:17785): libfprint-elanspi-DEBUG: 04:25:21.439: <guess> stddev=346514d, ip=0, is_fp=1, is_empty=0
(process:17785): libfprint-SSM-DEBUG: 04:25:21.528: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3
(process:17785): libfprint-SSM-DEBUG: 04:25:21.528: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:22.975: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:22.975: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4
(process:17785): libfprint-elanspi-DEBUG: 04:25:23.107: <guess> stddev=324160d, ip=0, is_fp=1, is_empty=0
(process:17785): libfprint-elanspi-DEBUG: 04:25:23.190: <fp_frame> diff = 107344
(process:17785): libfprint-SSM-DEBUG: 04:25:23.190: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3
(process:17785): libfprint-SSM-DEBUG: 04:25:23.191: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:25.263: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:25.264: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4
(process:17785): libfprint-elanspi-DEBUG: 04:25:25.335: <guess> stddev=339430d, ip=0, is_fp=1, is_empty=0
(process:17785): libfprint-elanspi-DEBUG: 04:25:25.404: <fp_frame> diff = 246471
(process:17785): libfprint-SSM-DEBUG: 04:25:25.404: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3
(process:17785): libfprint-SSM-DEBUG: 04:25:25.404: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
(process:17785): libfprint-SSM-DEBUG: 04:25:26.960: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully
(process:17785): libfprint-SSM-DEBUG: 04:25:26.960: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4
(process:17785): libfprint-elanspi-DEBUG: 04:25:27.030: <guess> stddev=334711d, ip=0, is_fp=1, is_empty=0
(process:17785): libfprint-elanspi-DEBUG: 04:25:27.097: <fp_frame> diff = 73010
(process:17785): libfprint-SSM-DEBUG: 04:25:27.098: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3
(process:17785): libfprint-SSM-DEBUG: 04:25:27.098: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0
** (umockdev-run:17773): DEBUG: 04:25:27.378: umockdev-utils.vala:50: umockdev: caught signal 15, propagating to child
** (umockdev-run:17773): DEBUG: 04:25:27.390: umockdev.vala:150: Removing test bed /tmp/umockdev.XOSOB2
(umockdev-run:17773): GLib-DEBUG: 04:25:27.449: unsetenv() is not thread-safe and should not be used after threads are created
----------------------------------- stderr -----------------------------------
libfprint-Message: 04:24:13.729: Failed to read spidev block size, using 4096
==============================================================================
================================== 113/116 ===================================
test: libfprint / udev-hwdb
start time: 04:25:27
duration: 0.13s
result: exit status 0
command: LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint:/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 MALLOC_PERTURB_=225 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /<<PKGBUILDDIR>>/tests/test-generated-hwdb.sh
==============================================================================
================================== 114/116 ===================================
test: libfprint:unit-tests / fpi-device
start time: 04:25:03
duration: 24.06s
result: exit status 0
command: LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint:/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MALLOC_PERTURB_=153 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device
----------------------------------- stdout -----------------------------------
# random seed: R02Sff1bdec1356c1a297991d93f875af1ba
1..97
# Start of driver tests
ok 1 /driver/get_driver
ok 2 /driver/get_device_id
ok 3 /driver/get_name
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.024: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.024: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.025: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.025: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.039: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.042: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.043: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.044: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 4 /driver/is_open
ok 5 /driver/get_nr_enroll_stages
ok 6 /driver/set_nr_enroll_stages
ok 7 /driver/supports_identify
ok 8 /driver/supports_capture
ok 9 /driver/has_storage
ok 10 /driver/do_not_support_identify
ok 11 /driver/do_not_support_capture
ok 12 /driver/has_not_storage
ok 13 /driver/get_usb_device
ok 14 /driver/get_virtual_env
ok 15 /driver/get_driver_data
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.072: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.073: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.074: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.077: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 16 /driver/initial_features
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.081: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.082: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.084: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.087: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 17 /driver/probe
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.090: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.092: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.093: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.094: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.097: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.098: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.099: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.101: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 18 /driver/open
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.104: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.105: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.106: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.109: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.113: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.114: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.115: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.116: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 19 /driver/close
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.119: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.120: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.121: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.122: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.127: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.130: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
# libfprint-device-DEBUG: Device reported enroll completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.130: Device reported enroll completion
# libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.131: Print for finger FP_FINGER_UNKNOWN enrolled
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.132: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.135: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.137: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.138: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.140: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.141: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 20 /driver/enroll
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.145: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.148: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.149: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.150: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.152: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.153: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
# libfprint-device-DEBUG: Device reported verify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.155: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.156: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.157: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.159: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.161: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.164: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.165: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.166: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 21 /driver/verify
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.170: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.171: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.172: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.174: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.19 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.366: Updated temperature model after 0.19 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:04.369: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported identify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:04.371: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.558: Device reported identify completion
# libfprint-device-DEBUG: Updated temperature model after 4.19 seconds, ratio 0.27 -> 0.29, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.559: Updated temperature model after 4.19 seconds, ratio 0.27 -> 0.29, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.560: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.561: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.680: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.680: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.680: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.12 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.681: Updated temperature model after 0.12 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 22 /driver/identify
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.682: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.682: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.683: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.683: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.684: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.685: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
# libfprint-device-DEBUG: Device reported capture completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.685: Device reported capture completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.685: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.686: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.686: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.687: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.687: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.687: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 23 /driver/capture
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.689: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.689: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.689: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.690: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.897: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
# libfprint-device-DEBUG: Device reported listing completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.897: Device reported listing completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.897: Completing action FPI_DEVICE_ACTION_LIST in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.21 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.898: Updated temperature model after 0.21 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.981: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.981: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.981: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.990: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 24 /driver/list
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.991: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.991: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.992: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.992: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.993: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
# libfprint-device-DEBUG: Device reported deletion completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.993: Device reported deletion completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.994: Completing action FPI_DEVICE_ACTION_DELETE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.994: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.995: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.995: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.995: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.996: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 25 /driver/delete
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.997: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.997: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.997: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.998: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:08.998: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
# libfprint-device-DEBUG: Device reported deletion completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.999: Device reported deletion completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.999: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:08.999: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.000: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.000: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.001: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.001: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 26 /driver/clear_storage
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.002: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.002: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.003: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.003: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Idle cancelling on ongoing operation!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.004: Idle cancelling on ongoing operation!
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.005: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.105: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
# libfprint-device-DEBUG: Device reported deletion completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.106: Device reported deletion completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.106: Completing action FPI_DEVICE_ACTION_DELETE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.106: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.108: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.108: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.108: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.108: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 27 /driver/cancel
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.110: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.110: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.111: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.111: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.112: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Idle cancelling on ongoing operation!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.113: Idle cancelling on ongoing operation!
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.113: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.114: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.115: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.115: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
# libfprint-device-DEBUG: Device reported verify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.115: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.116: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.116: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.116: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.126: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.126: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.126: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.127: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 28 /driver/critical
ok 29 /driver/get_current_action
ok 30 /driver/timeout
ok 31 /driver/error_types
ok 32 /driver/retry_error_types
# Start of get_scan_type tests
ok 33 /driver/get_scan_type/press
ok 34 /driver/get_scan_type/swipe
# End of get_scan_type tests
# Start of set_scan_type tests
ok 35 /driver/set_scan_type/press
ok 36 /driver/set_scan_type/swipe
# End of set_scan_type tests
# Start of finger_status tests
ok 37 /driver/finger_status/inactive
# libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED
ok 38 /driver/finger_status/waiting
# libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.184: Device reported finger status change: FP_FINGER_STATUS_PRESENT
ok 39 /driver/finger_status/present
# libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED
# libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
# libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.188: Device reported finger status change: FP_FINGER_STATUS_PRESENT
# libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.189: Device reported finger status change: FP_FINGER_STATUS_NONE
ok 40 /driver/finger_status/changes
# End of finger_status tests
# Start of features tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.201: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.202: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.203: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.204: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 41 /driver/features/probe_updates
# End of features tests
# Start of initial_features tests
ok 42 /driver/initial_features/none
ok 43 /driver/initial_features/no_capture
ok 44 /driver/initial_features/no_verify
ok 45 /driver/initial_features/no_identify
ok 46 /driver/initial_features/no_storage
ok 47 /driver/initial_features/no_list
ok 48 /driver/initial_features/no_delete
ok 49 /driver/initial_features/no_clear
# End of initial_features tests
# Start of probe tests
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.214: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.215: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.215: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 50 /driver/probe/error
# libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.226: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.227: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.228: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.229: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 51 /driver/probe/action_error
# End of probe tests
# Start of open tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.233: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.234: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.235: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.236: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 52 /driver/open/error
# End of open tests
# Start of close tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.239: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.240: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.241: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.241: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.242: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.242: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.243: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.243: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 53 /driver/close/error
# End of close tests
# Start of enroll tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.244: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.245: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.245: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.245: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.256: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.257: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
# libfprint-device-DEBUG: Device reported enroll completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.258: Device reported enroll completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.259: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.260: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.262: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.263: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.264: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.265: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 54 /driver/enroll/error
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.267: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.268: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.269: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.271: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.272: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Device reported enroll progress, reported 1963183905 of 1597779556 have been completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.273: Device reported enroll progress, reported 1963183905 of 1597779556 have been completed
# libfprint-device-DEBUG: Device reported enroll progress, reported 1640323761 of 1597779556 have been completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.279: Device reported enroll progress, reported 1640323761 of 1597779556 have been completed
# libfprint-device-DEBUG: Device reported enroll progress, reported 1811002825 of 1597779556 have been completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.280: Device reported enroll progress, reported 1811002825 of 1597779556 have been completed
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.281: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
# libfprint-device-DEBUG: Device reported enroll completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.282: Device reported enroll completion
# libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.283: Print for finger FP_FINGER_UNKNOWN enrolled
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.284: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.285: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.287: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.288: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.289: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.294: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 55 /driver/enroll/progress
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.297: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.298: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.299: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.300: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.301: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.301: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
# libfprint-device-DEBUG: Device reported enroll completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.301: Device reported enroll completion
# libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.302: Print for finger FP_FINGER_UNKNOWN enrolled
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.302: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.302: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.303: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.303: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.304: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.304: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 56 /driver/enroll/update_nbis
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.306: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.311: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.312: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.313: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.316: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.316: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.317: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.318: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 57 /driver/enroll/update_nbis_wrong_device
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.321: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.322: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.327: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.328: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.330: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.331: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.332: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.333: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 58 /driver/enroll/update_nbis_wrong_driver
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.336: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.336: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.338: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.346: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.348: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.349: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.350: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.351: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 59 /driver/enroll/update_nbis_missing_feature
# Start of error tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.354: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.354: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.355: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.356: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.358: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Device reported enroll completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.363: Device reported enroll completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.364: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.365: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.367: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Device reported enroll completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.368: Device reported enroll completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.369: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.370: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.371: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Device reported enroll completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.372: Device reported enroll completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.373: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.379: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.380: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.381: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.383: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.383: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 60 /driver/enroll/error/no_print
# End of error tests
# End of enroll tests
# Start of verify tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.387: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.388: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.389: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.389: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.395: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.396: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
# libfprint-device-DEBUG: Device reported verify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.397: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.398: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.399: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.400: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.402: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.403: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.404: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.405: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 61 /driver/verify/fail
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.416: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.417: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.418: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.418: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.419: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.420: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
# libfprint-device-DEBUG: Device reported verify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.420: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.420: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.420: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.421: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.422: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.422: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.422: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.423: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 62 /driver/verify/retry
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.424: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.424: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.425: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.425: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.428: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.429: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.430: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.431: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.432: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.434: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.439: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.440: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.441: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 63 /driver/verify/error
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.443: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.444: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.445: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.446: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.449: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.450: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.451: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.452: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 64 /driver/verify/not_supported
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.463: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.464: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.465: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.466: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.467: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Device reported verify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.468: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.469: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.470: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.470: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.472: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.473: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.474: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.475: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 65 /driver/verify/report_no_cb
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.482: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.483: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.484: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.485: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.486: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.487: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.488: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.489: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.491: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.492: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.502: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.503: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 66 /driver/verify/not_reported
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.506: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.507: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.508: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.509: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.510: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Device reported verify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.511: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.512: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.513: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.514: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.515: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Device reported verify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.516: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.517: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.518: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.519: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.520: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Device reported verify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.521: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.530: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.532: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.532: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.533: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Device reported verify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.533: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.534: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.534: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.534: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.535: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Device reported verify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.536: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.536: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.536: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.537: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.538: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.538: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.538: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.538: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 67 /driver/verify/complete_retry
# End of verify tests
# Start of identify tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.540: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.540: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.540: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.541: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.675: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.678: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported identify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.679: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.679: Device reported identify completion
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.679: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.680: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.680: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.741: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.742: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.743: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.744: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 68 /driver/identify/fail
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.747: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.748: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.749: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.750: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.14 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.886: Updated temperature model after 0.14 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.889: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported identify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.889: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.890: Device reported identify completion
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.891: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.892: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.893: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.954: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.954: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.955: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.956: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 69 /driver/identify/retry
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:09.959: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.960: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.960: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:09.961: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.096: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.099: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.099: Device reported identify completion
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.100: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.101: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.102: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.161: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.162: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.163: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.165: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 70 /driver/identify/error
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.301: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.301: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.302: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.14 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.303: Updated temperature model after 0.14 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.304: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.307: Device reported identify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.308: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.309: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.370: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.370: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.371: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.372: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 71 /driver/identify/not_reported
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.594: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.594: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.595: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.22 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.595: Updated temperature model after 0.22 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.595: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Device reported identify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.598: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.598: Device reported identify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.610: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.611: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.614: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Device reported identify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.616: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.616: Device reported identify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.617: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.617: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.637: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Device reported identify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.639: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.639: Device reported identify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.640: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.640: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.656: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.656: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.656: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.657: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 72 /driver/identify/complete_retry
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.753: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.753: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.754: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.754: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.755: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Device reported identify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.755: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.755: Device reported identify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.756: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.756: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.757: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.757: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.757: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.762: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 73 /driver/identify/report_no_cb
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.955: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.955: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.955: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.19 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.956: Updated temperature model after 0.19 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.964: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.965: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:10.965: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported identify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:10.966: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:14.868: Device reported identify completion
# libfprint-device-DEBUG: Updated temperature model after 3.91 seconds, ratio 0.27 -> 0.28, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:14.869: Updated temperature model after 3.91 seconds, ratio 0.27 -> 0.28, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:14.870: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:14.871: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:14.876: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:14.877: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:14.877: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:14.879: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 74 /driver/identify/suspend_continues
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:15.122: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:15.123: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:15.124: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.19 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:15.125: Updated temperature model after 0.19 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:15.134: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:15.138: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:15.139: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported identify result
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:15.140: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:19.824: Device reported identify completion
# libfprint-device-DEBUG: Updated temperature model after 4.70 seconds, ratio 0.27 -> 0.29, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:19.825: Updated temperature model after 4.70 seconds, ratio 0.27 -> 0.29, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:19.830: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:19.831: Updated temperature model after 0.01 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:19.836: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:19.837: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:19.842: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:19.843: Updated temperature model after 0.01 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 75 /driver/identify/suspend_succeeds
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:20.125: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.125: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.130: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.21 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.131: Updated temperature model after 0.21 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.133: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:20.136: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:20.137: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.142: Device reported identify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.143: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.144: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:20.149: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.150: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.151: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.152: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 76 /driver/identify/suspend_busy_error
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:20.243: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.244: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.245: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.245: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:20.248: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.249: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.250: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.251: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 77 /driver/identify/suspend_while_idle
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:20.460: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.461: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.462: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.21 seconds, ratio 0.27 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.463: Updated temperature model after 0.21 seconds, ratio 0.27 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.465: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.13 seconds, ratio 0.26 -> 0.31, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:20.596: Updated temperature model after 0.13 seconds, ratio 0.26 -> 0.31, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.31 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:22.596: Updated temperature model after 2.00 seconds, ratio 0.31 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT
# libfprint-device-DEBUG: Idle cancelling on ongoing operation!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:22.597: Idle cancelling on ongoing operation!
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:22.597: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:22.597: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:22.597: Device reported identify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:22.598: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:22.598: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:22.601: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:22.610: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
# libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:24.690: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.794: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.795: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.795: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.795: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.796: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 78 /driver/identify/warmup_cooldown
# End of identify tests
# Start of capture tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.870: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.870: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.870: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.871: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.872: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.872: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.873: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.873: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 79 /driver/capture/not_supported
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.874: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.874: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.875: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.875: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.876: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.876: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
# libfprint-device-DEBUG: Device reported capture completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.876: Device reported capture completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.877: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.877: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.878: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.878: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.878: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.879: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 80 /driver/capture/error
# End of capture tests
# Start of list tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.880: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.880: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.881: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.881: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.882: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
# libfprint-device-DEBUG: Device reported listing completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.882: Device reported listing completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.882: Completing action FPI_DEVICE_ACTION_LIST in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.883: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.883: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.884: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.884: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.884: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 81 /driver/list/error
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.886: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.886: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.886: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.887: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.888: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.888: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.888: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.889: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 82 /driver/list/no_storage
# End of list tests
# Start of delete tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.890: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.890: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.891: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.891: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.892: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
# libfprint-device-DEBUG: Device reported deletion completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.892: Device reported deletion completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.892: Completing action FPI_DEVICE_ACTION_DELETE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.893: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.894: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.894: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.894: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.895: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 83 /driver/delete/error
# End of delete tests
# Start of clear_storage tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.896: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.896: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.896: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.897: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.898: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
# libfprint-device-DEBUG: Device reported deletion completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.898: Device reported deletion completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.898: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.898: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.899: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.899: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.900: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.900: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 84 /driver/clear_storage/error
# End of clear_storage tests
# Start of cancel tests
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.901: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.902: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.902: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.902: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.903: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
# libfprint-device-DEBUG: Device reported deletion completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.904: Device reported deletion completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.904: Completing action FPI_DEVICE_ACTION_DELETE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.904: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.905: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.906: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.906: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.906: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 85 /driver/cancel/fail
# End of cancel tests
# Start of get_current_action tests
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.908: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.908: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.908: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.909: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.909: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.910: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.910: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 86 /driver/get_current_action/open
# End of get_current_action tests
# Start of get_cancellable tests
ok 87 /driver/get_cancellable/error
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.912: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.912: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.913: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.913: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.914: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.914: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.914: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 88 /driver/get_cancellable/open
# Start of open tests
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.916: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.916: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.916: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.917: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.917: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.918: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.918: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 89 /driver/get_cancellable/open/internal
# End of open tests
# End of get_cancellable tests
# Start of action_is_cancelled tests
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.919: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.920: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.920: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.921: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.921: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.922: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.925: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 90 /driver/action_is_cancelled/open
ok 91 /driver/action_is_cancelled/error
# Start of open tests
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.927: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.927: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.928: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.928: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.929: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.929: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.929: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
ok 92 /driver/action_is_cancelled/open/internal
# End of open tests
# End of action_is_cancelled tests
# Start of complete_action tests
# Start of all tests
ok 93 /driver/complete_action/all/error
# End of all tests
# End of complete_action tests
# Start of action_error tests
ok 94 /driver/action_error/error
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.932: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.933: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.933: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.933: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.933: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.934: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.934: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.935: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.935: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.936: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.936: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
# libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.937: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL
# libfprint-device-DEBUG: Device reported enroll completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.937: Device reported enroll completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.937: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.937: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.938: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.939: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
# libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.939: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.939: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.940: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.940: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.941: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.941: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.941: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.941: Device reported identify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.942: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.942: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.943: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.943: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
# libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.944: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE
# libfprint-device-DEBUG: Device reported capture completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.944: Device reported capture completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.944: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.945: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.945: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
# libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.946: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST
# libfprint-device-DEBUG: Device reported listing completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.946: Device reported listing completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.946: Completing action FPI_DEVICE_ACTION_LIST in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.947: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.947: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
# libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.948: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE
# libfprint-device-DEBUG: Device reported deletion completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.948: Device reported deletion completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.948: Completing action FPI_DEVICE_ACTION_DELETE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.949: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.949: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
# libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.950: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE
# libfprint-device-DEBUG: Device reported deletion completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.950: Device reported deletion completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.950: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.951: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.951: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.952: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.952: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.952: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.952: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 95 /driver/action_error/all
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.955: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.955: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.956: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.957: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.957: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.957: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.958: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.959: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.959: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
# libfprint-device-DEBUG: Device reported enroll completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.959: Device reported enroll completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.960: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.960: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.961: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.961: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
# libfprint-device-DEBUG: Device reported verify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.962: Device reported verify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.962: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.962: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.963: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.964: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
# libfprint-device-DEBUG: Device reported identify completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.964: Device reported identify completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.964: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.965: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.965: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.966: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
# libfprint-device-DEBUG: Device reported capture completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.966: Device reported capture completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.967: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.967: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.968: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
# libfprint-device-DEBUG: Device reported listing completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.968: Device reported listing completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.968: Completing action FPI_DEVICE_ACTION_LIST in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.969: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.970: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
# libfprint-device-DEBUG: Device reported deletion completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.970: Device reported deletion completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.970: Completing action FPI_DEVICE_ACTION_DELETE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.971: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.971: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
# libfprint-device-DEBUG: Device reported deletion completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.972: Device reported deletion completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.972: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.972: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
# libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
#
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-fake_test_dev-DEBUG: 04:25:27.973: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.973: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.974: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fpi-device:17960): libfprint-device-DEBUG: 04:25:27.974: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
ok 96 /driver/action_error/fail
# End of action_error tests
# Start of timeout tests
ok 97 /driver/timeout/cancelled
# End of timeout tests
# End of driver tests
==============================================================================
================================== 115/116 ===================================
test: libfprint:unit-tests / fp-device
start time: 04:25:24
duration: 4.91s
result: exit status 0
command: LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint:/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf FP_DRIVERS_WHITELIST=virtual_image:virtual_device:virtual_device_storage UDEV_HWDB_CHECK_CONTENTS=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> FP_DEVICE_EMULATION=1 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints UDEV_HWDB=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint/fprint-list-udev-hwdb G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests MALLOC_PERTURB_=196 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device
----------------------------------- stdout -----------------------------------
# random seed: R02S7bef2849b262e8bb1ff36b61f1ee16cf
1..17
# Start of device tests
# Start of async tests
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:24.971: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.022: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.023: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.023: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.023: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.024: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.024: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.024: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-LJ4LB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.025: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-LJ4LB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.031: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.055: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.055: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.056: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:25.057: 38978024654921: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:25.058: 38978024656375: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:25.162: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.162: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.163: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.163: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:25.164: 38978024761862: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:25.266: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.266: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.267: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.267: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:25.275: unsetenv() is not thread-safe and should not be used after threads are created
ok 1 /device/async/open
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:25.276: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.276: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.308: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.308: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.309: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.309: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.309: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.310: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.310: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-3HT6A2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.310: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-3HT6A2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.311: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.330: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.331: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.331: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:25.332: 38978024930277: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:25.332: 38978024930570: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:25.434: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.435: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.435: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.435: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:25.436: 38978025034157: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:25.537: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.537: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.537: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.538: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:25.546: unsetenv() is not thread-safe and should not be used after threads are created
ok 2 /device/async/close
# End of async tests
# Start of sync tests
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:25.547: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.548: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.577: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.578: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.578: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.578: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.579: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.579: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.579: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-4G6NB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.579: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-4G6NB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.580: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.609: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.609: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.610: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:25.611: 38978025208777: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:25.611: 38978025209099: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:25.713: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.713: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.713: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.714: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:25.715: 38978025313016: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:25.815: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.816: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.816: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.817: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:25.819: unsetenv() is not thread-safe and should not be used after threads are created
ok 3 /device/sync/open
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:25.820: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.820: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.849: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.849: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.850: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.854: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.854: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.855: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.855: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-1PUIB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.855: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-1PUIB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:25.856: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.874: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.874: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.875: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:25.875: 38978025473435: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:25.875: 38978025473696: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:25.978: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.978: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.979: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:25.979: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:25.979: 38978025577705: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:26.082: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.082: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.083: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.083: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:26.094: unsetenv() is not thread-safe and should not be used after threads are created
ok 4 /device/sync/close
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:26.095: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.095: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.125: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.125: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.125: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.126: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.126: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.126: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.126: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-T3DBB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.127: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-T3DBB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.127: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.141: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.142: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.150: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:26.151: 38978025749078: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:26.151: 38978025749339: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:26.258: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.258: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.259: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.259: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:26.260: 38978025857952: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:26.362: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.362: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.363: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.363: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:26.374: unsetenv() is not thread-safe and should not be used after threads are created
ok 5 /device/sync/get_driver
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:26.375: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.375: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.406: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.406: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.407: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.407: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.407: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.408: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.408: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-N925A2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.408: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-N925A2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.409: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.430: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.431: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.431: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:26.432: 38978026030129: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:26.432: 38978026030389: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:26.538: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.538: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.539: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.539: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:26.540: 38978026137757: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:26.642: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.642: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.643: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.643: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:26.658: unsetenv() is not thread-safe and should not be used after threads are created
ok 6 /device/sync/get_device_id
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:26.659: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.659: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.685: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.685: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.685: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.686: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.692: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.692: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.693: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Z3IQB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.693: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Z3IQB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.693: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.712: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.712: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.712: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:26.713: 38978026311305: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:26.713: 38978026311571: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:26.818: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.818: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.819: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.819: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:26.820: 38978026417839: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:26.920: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.921: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.921: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:26.921: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:26.934: unsetenv() is not thread-safe and should not be used after threads are created
ok 7 /device/sync/get_name
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:26.935: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.935: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.968: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.968: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.969: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.969: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.969: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.970: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.978: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-XHBLB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.978: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-XHBLB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:26.979: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.008: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.009: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.009: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:27.010: 38978026608292: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:27.010: 38978026608605: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:27.114: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.114: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.115: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.115: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:27.116: 38978026713934: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:27.218: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.218: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.219: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.219: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:27.227: unsetenv() is not thread-safe and should not be used after threads are created
ok 8 /device/sync/get_scan_type
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:27.228: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.228: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.263: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.263: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.263: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.263: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.264: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.264: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.264: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-5B6DB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.265: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-5B6DB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.265: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.280: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.281: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.281: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:27.286: 38978026884539: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:27.287: 38978026884890: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:27.390: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.390: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.391: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.391: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:27.392: 38978026989846: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:27.494: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.494: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.495: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.495: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:27.499: unsetenv() is not thread-safe and should not be used after threads are created
ok 9 /device/sync/get_finger_status
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:27.500: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.500: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.538: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.539: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.539: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.539: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.539: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.540: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.540: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-NDV8A2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.540: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-NDV8A2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.555: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.578: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.579: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.579: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:27.580: 38978027177873: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:27.580: 38978027178167: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:27.682: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.682: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.682: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.683: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:27.683: 38978027281377: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:27.784: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.784: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.784: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.785: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:27.787: unsetenv() is not thread-safe and should not be used after threads are created
ok 10 /device/sync/get_nr_enroll_stages
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:27.788: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.788: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.828: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.829: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.829: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.829: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.830: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.830: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.830: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-J84HB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.831: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-J84HB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:27.831: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.860: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.860: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.861: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:27.862: 38978027459750: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:27.870: 38978027468107: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:27.974: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.974: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.975: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:27.975: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:27.976: 38978027573927: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:28.076: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.077: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.077: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.078: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:28.083: unsetenv() is not thread-safe and should not be used after threads are created
ok 11 /device/sync/supports_identify
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:28.084: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.084: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.125: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.125: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.126: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.126: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.126: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.127: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.127: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0OGBB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.127: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0OGBB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.128: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.156: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.156: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.157: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:28.157: 38978027755637: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:28.158: 38978027755932: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:28.270: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.270: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.271: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.271: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:28.272: 38978027869987: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:28.374: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.374: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.375: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.375: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:28.378: unsetenv() is not thread-safe and should not be used after threads are created
ok 12 /device/sync/supports_capture
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:28.378: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.379: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.420: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.420: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.420: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.421: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.421: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.421: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.422: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-4YJ6A2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.430: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-4YJ6A2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.431: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.452: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.452: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.453: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:28.453: 38978028051688: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:28.462: 38978028051980: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:28.564: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.564: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.564: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.565: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:28.565: 38978028163640: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:28.666: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.666: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.667: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.667: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:28.675: unsetenv() is not thread-safe and should not be used after threads are created
ok 13 /device/sync/has_storage
# Start of open tests
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:28.676: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.676: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.712: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.713: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.713: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.713: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.714: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.714: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.714: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-MN1QB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.715: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-MN1QB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.715: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.733: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.734: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.735: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:28.736: 38978028334257: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:28.737: 38978028334871: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:28.839: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.840: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.841: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.842: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:28.843: 38978028441637: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:28.944: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.945: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.946: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:28.947: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:28.955: unsetenv() is not thread-safe and should not be used after threads are created
ok 14 /device/sync/open/notify
# End of open tests
# Start of close tests
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:28.958: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.958: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.993: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.998: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:28.999: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.000: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.001: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.002: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.003: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-VFPLB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.004: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-VFPLB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.005: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.030: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.031: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.032: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:29.033: 38978028631369: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:29.034: 38978028632226: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:29.137: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.137: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.139: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.140: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:29.141: 38978028739258: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:29.242: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.243: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.244: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.245: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:29.251: unsetenv() is not thread-safe and should not be used after threads are created
ok 15 /device/sync/close/notify
# End of close tests
# Start of identify tests
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:29.253: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.254: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.290: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.291: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.291: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.292: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.293: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.302: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.304: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-OJ1EB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.305: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-OJ1EB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.306: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.324: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.325: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.326: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:29.327: 38978028925192: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:29.328: 38978028925826: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:29.430: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.431: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.432: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.433: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:29.435: 38978029032961: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:29.539: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.539: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.540: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.541: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:29.545: unsetenv() is not thread-safe and should not be used after threads are created
ok 16 /device/sync/identify/cancelled
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:29.547: setenv()/putenv() are not thread-safe and should not be used after threads are created
# libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.6)
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.548: Initializing FpContext (libfprint version 1.94.6)
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.581: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0BDA:5401
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.582: No driver found for USB device 0BDA:5401
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.584: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0003
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.585: No driver found for USB device 1D6B:0003
# libfprint-context-DEBUG: No driver found for USB device 0624:0249
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.585: No driver found for USB device 0624:0249
# libfprint-context-DEBUG: No driver found for USB device 0624:0248
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.590: No driver found for USB device 0624:0248
# libfprint-context-DEBUG: No driver found for USB device 1D6B:0002
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.591: No driver found for USB device 1D6B:0002
# libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-TB6NB2/virtual_image.socket
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.592: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-TB6NB2/virtual_image.socket
# libfprint-context-DEBUG: created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-context-DEBUG: 04:25:29.593: created
# libfprint-device-DEBUG: Device reported probe completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.610: Device reported probe completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.611: Completing action FPI_DEVICE_ACTION_PROBE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.612: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:29.613: 38978029211155: ../libfprint/drivers/virtual-image.c:216
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_device_connection-DEBUG: 04:25:29.614: 38978029211750: ../libfprint/drivers/virtual-device-listener.c:153
# libfprint-image_device-DEBUG: Image device open completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:29.722: Image device open completed
# libfprint-device-DEBUG: Device reported open completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.723: Device reported open completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.724: Completing action FPI_DEVICE_ACTION_OPEN in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.725: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-virtual_image-DEBUG: 04:25:29.727: 38978029324888: ../libfprint/drivers/virtual-image.c:244
# libfprint-image_device-DEBUG: Image device close completed
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-image_device-DEBUG: 04:25:29.830: Image device close completed
# libfprint-device-DEBUG: Device reported close completion
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.831: Device reported close completion
# libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.832: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
# libfprint-device-DEBUG: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): libfprint-device-DEBUG: 04:25:29.833: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
(/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests/test-fp-device:18021): GLib-DEBUG: 04:25:29.836: unsetenv() is not thread-safe and should not be used after threads are created
ok 17 /device/sync/identify/null-prints
# End of identify tests
# End of sync tests
# End of device tests
==============================================================================
================================== 116/116 ===================================
test: libfprint:drivers / vfs7552
start time: 04:24:28
duration: 75.54s
result: killed by signal 15 SIGTERM
command: G_DEBUG=fatal-warnings MESON_BUILD_ROOT=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint FP_DEVICE_EMULATION=1 NO_AT_BRIDGE=1 MESON_SOURCE_ROOT=/<<PKGBUILDDIR>> MALLOC_PERTURB_=74 G_MESSAGES_DEBUG=all G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests FP_PRINTS_PATH=/<<PKGBUILDDIR>>/examples/prints G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/tests FP_DRIVERS_WHITELIST=vfs7552 GI_TYPELIB_PATH=/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/libfprint /usr/bin/python3 /<<PKGBUILDDIR>>/tests/umockdev-test.py /<<PKGBUILDDIR>>/tests/vfs7552
----------------------------------- stdout -----------------------------------
** (umockdev-run:17871): DEBUG: 04:24:28.711: umockdev.vala:123: Created udev test bed /tmp/umockdev.P88QB2
** (umockdev-run:17871): DEBUG: 04:24:28.712: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7
** (umockdev-run:17871): DEBUG: 04:24:28.740: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb)
** (umockdev-run:17871): DEBUG: 04:24:28.813: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.P88QB2/dev/bus/usb/001/003
** (umockdev-run:17871): DEBUG: 04:24:28.827: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
** (umockdev-run:17871): DEBUG: 04:24:28.837: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
** (umockdev-run:17871): DEBUG: 04:24:28.891: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.P88QB2/dev/bus/usb/001/001
** (umockdev-run:17871): DEBUG: 04:24:28.899: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0
** (umockdev-run:17871): DEBUG: 04:24:28.903: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
(umockdev-run:17871): GLib-GIO-DEBUG: 04:24:28.931: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
(umockdev-run:17871): GLib-DEBUG: 04:24:29.058: pidfd_open(17874) failed with error: Function not implemented
(process:17874): libfprint-context-DEBUG: 04:24:29.428: Initializing FpContext (libfprint version 1.94.6)
(process:17874): libfprint-context-DEBUG: 04:24:29.459: No driver found for USB device 1D6B:0002
(process:17874): libfprint-device-DEBUG: 04:24:29.462: Device reported probe completion
(process:17874): libfprint-device-DEBUG: 04:24:29.463: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:17874): libfprint-device-DEBUG: 04:24:29.463: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17874): libfprint-SSM-DEBUG: 04:24:29.520: [vfs7552] DEV_OPEN_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:29.520: [vfs7552] DEVICE OPEN entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.520: Sending vfs7552_cmd_01
(process:17874): libfprint-SSM-DEBUG: 04:24:29.549: [vfs7552] DEVICE OPEN entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.549: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.577: Got 38 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:29.577: [vfs7552] DEVICE OPEN entering state 2
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.577: Sending vfs7552_cmd_19
(process:17874): libfprint-SSM-DEBUG: 04:24:29.607: [vfs7552] DEVICE OPEN entering state 3
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.607: Receiving 128 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.634: Got 68 bytes out of 128
(process:17874): libfprint-SSM-DEBUG: 04:24:29.634: [vfs7552] DEVICE OPEN entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.634: Sending vfs7552_init_00
(process:17874): libfprint-SSM-DEBUG: 04:24:29.660: [vfs7552] DEVICE OPEN entering state 5
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.660: Receiving 64 bytes
(process:17874): libfprint-SSM-DEBUG: 04:24:29.694: [vfs7552] DEVICE OPEN entering state 6
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.694: Sending vfs7552_init_01
(process:17874): libfprint-SSM-DEBUG: 04:24:29.720: [vfs7552] DEVICE OPEN entering state 7
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.720: Receiving 64 bytes
(process:17874): libfprint-SSM-DEBUG: 04:24:29.745: [vfs7552] DEVICE OPEN entering state 8
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.746: Sending vfs7552_init_02
(process:17874): libfprint-SSM-DEBUG: 04:24:29.771: [vfs7552] DEVICE OPEN entering state 9
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.771: Receiving 64 bytes
(process:17874): libfprint-SSM-DEBUG: 04:24:29.798: [vfs7552] DEVICE OPEN entering state 10
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.799: Sending vfs7552_init_03
(process:17874): libfprint-SSM-DEBUG: 04:24:29.824: [vfs7552] DEVICE OPEN entering state 11
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.824: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.857: Got 10 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:29.857: [vfs7552] DEVICE OPEN entering state 12
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.857: Sending vfs7552_init_04
(process:17874): libfprint-SSM-DEBUG: 04:24:29.890: [vfs7552] DEVICE OPEN entering state 13
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.891: Receiving 64 bytes
(process:17874): libfprint-SSM-DEBUG: 04:24:29.916: [vfs7552] DEVICE OPEN completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:29.916: [vfs7552] DEV_OPEN_NUM_STATES completed successfully
(process:17874): libfprint-image_device-DEBUG: 04:24:29.916: Image device open completed
(process:17874): libfprint-device-DEBUG: 04:24:29.917: Device reported open completion
(process:17874): libfprint-device-DEBUG: 04:24:29.917: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:17874): libfprint-device-DEBUG: 04:24:29.917: Updated temperature model after 0.45 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17874): libfprint-device-DEBUG: 04:24:29.919: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:17874): libfprint-image_device-DEBUG: 04:24:29.919: Activating image device
(process:17874): libfprint-image_device-DEBUG: 04:24:29.919: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:17874): libfprint-image_device-DEBUG: 04:24:29.920: Image device activation completed
(process:17874): libfprint-image_device-DEBUG: 04:24:29.920: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:17874): libfprint-image_device-DEBUG: 04:24:29.920: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:17874): libfprint-device-DEBUG: 04:24:29.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.968: changing to 4
(process:17874): libfprint-SSM-DEBUG: 04:24:29.969: [vfs7552] ACTIVATE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:29.969: [vfs7552] ACTIVATE INIT entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.969: Sending vfs7552_image_start
(process:17874): libfprint-SSM-DEBUG: 04:24:29.997: [vfs7552] ACTIVATE INIT entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:29.997: Receiving 2048 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.026: Got 1962 bytes out of 2048
(process:17874): libfprint-SSM-DEBUG: 04:24:30.026: [vfs7552] ACTIVATE INIT completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.026: [vfs7552] ACTIVATE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.026: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.026: Receiving 8 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.052: Got 5 bytes out of 8
(process:17874): libfprint-SSM-DEBUG: 04:24:30.052: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.052: [vfs7552] ACTIVATE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:30.052: [vfs7552] ACTIVATE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.053: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.053: Receiving 8 bytes
(process:17874): libfprint-device-DEBUG: 04:24:30.074: Updated temperature model after 0.15 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.085: Got 5 bytes out of 8
(process:17874): libfprint-SSM-DEBUG: 04:24:30.085: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.085: [vfs7552] ACTIVATE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:30.086: [vfs7552] ACTIVATE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:30.086: [vfs7552] ACTIVATE_NUM_STATES completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.086: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.086: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.086: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.112: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.112: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.148: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.148: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.149: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.149: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.149: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.149: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.175: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.175: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.203: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.203: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.203: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.203: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.203: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.203: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.230: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.230: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.262: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.262: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.262: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.262: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.262: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.262: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.289: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.289: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.317: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.317: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.317: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.317: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.317: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.317: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.351: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.351: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.380: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.380: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.380: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.380: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.380: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.380: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.411: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.411: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.443: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.443: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.443: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.443: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.443: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.443: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.471: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.471: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.505: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.505: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.505: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.505: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.505: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.505: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.533: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.533: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.571: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.571: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.571: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.571: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.571: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.571: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.593: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.594: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.623: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.623: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.623: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.623: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.623: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.623: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.655: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.655: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.684: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.684: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.684: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.684: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.684: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.684: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.711: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.711: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.745: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.745: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.745: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.745: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.745: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.745: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.772: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.772: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.802: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.802: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.802: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.802: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.802: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.802: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.829: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.829: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.862: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.862: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.862: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.862: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.862: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.862: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.889: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.889: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.918: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.922: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.922: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.922: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.922: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.922: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:30.950: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.950: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.978: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:30.978: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:30.978: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:30.978: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:30.978: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:30.979: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:31.005: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.005: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.038: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:31.038: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:31.038: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:31.038: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:31.039: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.039: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:31.066: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.066: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.095: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:31.096: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:31.096: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:31.096: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:31.096: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.096: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:31.128: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.128: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.157: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:31.157: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:31.157: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:31.157: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:31.157: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.157: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:31.217: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.217: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.480: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:31.480: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:31.480: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:31.480: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:31.480: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.480: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:31.525: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.525: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.611: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:31.613: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:31.650: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:31.650: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:31.650: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.650: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:31.727: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.727: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.811: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:31.811: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:31.811: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:31.811: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:31.812: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.812: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:31.846: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.846: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.883: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:31.884: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:31.884: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:31.884: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:31.884: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.884: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:31.922: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.922: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.965: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:31.965: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:31.965: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:31.965: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:31.966: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:31.966: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.005: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.005: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.058: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.059: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.059: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.059: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.059: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.059: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.099: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.099: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.141: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.142: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.142: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.142: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.146: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.146: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.183: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.183: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.224: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.224: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.224: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.224: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.224: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.225: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.263: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.263: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.305: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.305: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.305: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.306: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.306: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.306: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.342: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.342: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.385: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.385: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.385: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.385: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.385: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.385: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.425: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.425: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.464: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.464: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.464: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.464: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.464: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.464: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.499: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.499: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.532: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.532: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.532: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.532: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.532: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.532: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.567: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.567: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.600: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.600: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.600: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.600: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.600: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.600: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.627: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.627: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.663: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.663: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.663: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.663: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.663: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.663: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.690: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.690: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.719: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.719: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.719: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.719: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.719: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.719: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.750: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.750: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.783: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.783: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.783: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.783: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.783: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.783: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.810: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.810: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.843: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.843: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.843: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.843: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.844: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.844: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.874: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.874: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.901: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.901: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.901: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.901: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.901: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.901: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.933: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.933: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.962: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:32.962: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:32.963: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:32.963: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:32.963: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.963: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:32.994: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:32.994: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.025: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.025: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.025: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.025: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.025: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.025: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.052: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.052: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.090: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.090: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.090: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.090: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.090: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.090: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.112: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.112: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.134: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.134: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.134: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.134: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.134: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.134: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.155: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.155: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.201: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.201: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.201: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.201: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.201: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.201: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.220: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.220: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.241: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.241: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.241: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.241: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.241: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.241: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.272: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.273: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.310: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.310: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.310: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.310: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.310: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.310: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.337: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.337: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.379: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.379: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.379: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.379: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.379: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.379: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.410: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.411: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.444: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.444: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.444: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.444: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.444: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.445: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.476: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.476: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.505: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.505: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.505: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.505: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.505: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.506: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.537: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.537: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.565: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.565: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.565: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.565: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.565: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.565: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.596: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.597: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.630: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.630: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.630: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.630: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.631: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.631: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.657: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.658: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.691: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.691: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.691: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.691: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.691: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.691: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.718: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.718: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.743: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.743: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.743: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.743: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.743: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.743: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.767: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.767: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.789: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.789: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.789: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.789: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.789: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.789: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.811: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.811: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.833: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.833: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.833: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.833: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.833: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.833: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.855: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.855: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.877: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.877: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.877: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.878: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.878: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.878: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.898: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.898: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.923: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.923: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.923: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.923: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.923: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.923: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.943: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.943: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.967: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:33.967: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:33.967: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:33.967: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:33.968: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.968: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:33.987: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:33.987: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.009: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.010: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.010: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.010: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.010: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.010: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.039: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.039: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.083: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.083: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.083: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.083: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.083: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.083: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.122: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.122: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.162: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.162: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.162: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.162: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.162: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.162: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.197: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.198: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.239: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.239: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.239: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.240: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.240: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.240: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.278: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.279: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.321: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.322: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.322: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.322: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.322: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.322: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.360: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.360: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.395: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.395: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.395: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.396: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.396: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.396: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.429: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.429: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.460: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.461: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.461: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.461: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.461: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.461: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.484: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.484: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.516: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.516: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.516: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.516: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.516: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.516: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.543: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.543: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.570: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.570: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.570: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.570: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.570: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.570: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.596: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.596: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.632: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.632: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.632: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.632: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.632: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.632: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.659: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.659: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.687: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.687: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.687: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.687: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.687: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.687: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.713: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.714: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.746: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.746: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.746: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.746: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.746: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.746: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.773: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.773: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.801: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.801: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.801: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.801: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.802: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.802: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.832: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.832: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.864: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.864: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.864: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.864: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.864: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.864: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.891: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.891: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.918: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.918: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.918: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.919: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.919: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.919: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:34.944: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.944: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.976: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:34.976: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:34.976: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:34.976: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:34.976: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:34.976: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.006: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.006: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.033: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.034: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.034: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.034: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.034: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.034: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.060: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.060: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.087: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.087: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.087: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.087: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.088: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.088: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.113: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.113: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.149: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.149: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.150: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.150: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.150: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.150: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.175: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.175: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.203: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.203: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.203: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.203: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.204: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.204: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.229: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.229: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.261: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.261: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.261: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.261: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.261: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.261: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.287: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.287: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.323: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.323: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.323: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.323: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.323: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.323: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.349: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.350: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.374: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.382: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.382: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.382: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.382: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.382: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.408: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.408: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.432: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.432: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.432: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.432: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.432: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.432: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.462: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.462: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.490: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.490: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.490: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.491: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.491: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.491: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.516: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.516: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.544: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.544: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.544: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.544: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.544: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.544: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.569: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.570: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.601: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.601: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.601: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.601: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.602: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.602: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.627: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.627: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.659: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.659: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.659: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.659: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.659: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.659: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.686: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.686: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.714: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.714: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.714: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.715: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.715: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.715: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.741: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.741: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.775: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.775: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.775: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.775: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.775: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.775: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.801: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.801: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.833: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.833: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.833: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.833: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.834: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.834: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.859: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.859: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.888: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.888: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.888: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.888: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.888: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.888: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.918: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.918: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.950: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:35.950: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:35.950: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:35.950: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:35.950: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.950: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:35.977: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:35.977: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.005: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.006: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.006: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.006: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.006: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.006: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.036: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.036: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.061: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.061: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.061: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.061: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.061: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.061: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.092: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.092: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.117: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.117: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.118: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.118: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:36.118: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.118: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:36.144: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.144: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:36.173: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:36.173: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.173: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:36.204: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.204: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:36.238: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:36.238: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.238: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:36.261: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.261: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:36.302: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.302: variance_before = 396
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.302: background stored
(process:17874): libfprint-SSM-DEBUG: 04:24:36.302: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.302: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.302: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.333: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.333: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.360: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.361: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.361: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.361: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.361: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.361: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.395: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.395: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.419: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.419: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.419: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.419: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.420: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.420: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.445: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.446: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.478: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.478: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.478: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.478: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.478: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.478: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.504: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.504: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.536: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.536: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.536: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.536: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.536: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.536: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.568: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.568: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.592: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.592: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.592: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.592: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.592: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.592: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.613: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.613: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.634: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.635: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.635: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.635: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.635: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.635: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.653: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.653: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.674: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.674: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.674: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.674: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.674: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.674: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.694: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.694: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.714: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.714: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.714: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.714: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.715: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.715: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.734: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.734: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.754: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.754: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.755: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.755: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.755: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.755: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.774: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.774: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.795: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.795: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.795: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.795: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.795: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.795: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.814: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.815: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.836: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.836: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.836: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.836: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.836: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.836: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.856: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.856: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.879: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.879: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.879: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.879: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.879: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.879: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.899: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.899: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.919: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.919: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.919: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.919: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.920: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.920: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.938: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.938: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.959: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:36.959: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:36.959: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:36.959: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:36.959: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.959: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:36.978: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.978: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:36.999: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.000: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.000: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.000: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.000: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.000: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.018: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.018: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.040: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.040: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.040: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.040: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.040: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.040: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.061: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.061: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.083: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.083: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.083: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.083: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.083: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.083: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.104: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.104: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.127: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.127: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.127: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.127: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.127: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.127: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.147: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.147: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.169: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.169: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.169: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.170: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.170: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.170: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.189: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.189: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.213: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.213: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.213: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.213: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.213: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.213: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.232: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.232: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.253: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.253: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.254: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.254: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.254: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.254: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.272: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.273: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.294: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.294: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.294: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.294: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.294: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.294: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.313: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.313: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.335: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.335: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.335: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.335: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.335: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.335: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.355: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.355: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.376: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.377: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.377: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.377: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.377: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.377: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.398: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.399: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.421: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.421: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.421: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.421: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.421: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.421: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.440: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.440: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.463: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.463: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.463: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.463: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.463: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.463: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.484: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.484: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.508: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.508: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.508: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.508: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.508: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.509: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.529: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.529: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.551: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.552: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.552: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.552: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.552: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.552: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.574: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.574: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.599: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.600: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.600: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.600: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.600: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.600: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.619: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.619: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.640: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.640: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.640: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.640: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.640: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.640: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.659: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.659: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.680: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.680: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.680: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.680: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.680: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.680: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.699: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.699: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.720: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.720: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.720: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.720: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.720: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.720: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.739: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.739: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.761: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.761: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.761: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.761: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.761: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.761: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.781: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.781: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.804: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.804: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.804: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.804: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.804: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.804: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.827: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.827: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.849: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.849: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.849: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.850: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.850: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.850: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.869: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.869: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.891: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.891: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.892: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.892: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.892: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.892: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.912: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.912: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.936: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.936: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.936: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.936: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.936: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.936: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.956: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.956: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.978: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:37.978: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:37.978: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:37.978: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:37.978: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.978: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:37.999: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:37.999: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.020: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.020: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.020: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.020: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.020: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.020: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.039: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.039: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.061: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.061: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.061: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.061: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.061: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.061: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.081: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.081: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.107: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.107: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.108: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.108: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.108: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.108: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.127: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.127: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.152: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.152: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.152: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.152: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.152: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.152: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.171: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.171: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.195: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.195: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.195: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.195: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.195: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.195: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.214: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.214: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.235: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.235: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.235: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.235: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.235: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.235: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.254: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.254: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.275: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.275: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.275: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.275: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.275: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.276: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.301: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.301: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.322: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.322: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.322: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.322: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.322: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.322: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.341: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.341: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.362: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.362: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.362: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.362: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.362: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.363: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.381: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.382: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.404: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.404: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.404: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.404: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.404: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.404: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.424: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.424: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.447: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.447: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.447: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.447: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.447: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.447: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.467: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.467: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.489: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.489: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.489: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.489: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.489: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.489: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.508: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.509: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.530: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.530: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.530: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.531: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.531: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.531: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.550: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.550: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.572: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.572: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.572: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.573: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.573: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.573: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.601: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.601: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.630: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.630: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.630: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.631: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.631: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.631: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.657: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.658: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.695: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.695: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.695: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.695: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.695: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.695: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.721: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.721: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.751: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.751: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.751: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.751: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.751: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.751: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.778: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.778: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.811: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.811: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.811: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.811: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.811: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.812: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.838: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.839: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.871: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.871: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.871: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.871: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.871: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.871: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.898: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.898: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.921: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.921: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.921: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.921: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.921: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.922: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.940: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.940: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.961: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:38.961: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:38.961: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:38.961: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:38.961: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.961: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:38.980: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:38.980: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.001: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.001: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.001: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.002: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.002: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.002: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.022: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.022: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.046: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.046: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.046: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.046: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.046: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.046: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.066: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.066: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.088: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.088: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.088: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.088: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.088: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.088: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.108: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.108: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.130: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.130: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.130: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.130: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.130: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.131: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.150: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.150: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.171: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.172: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.172: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.172: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.172: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.172: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.192: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.192: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.217: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.217: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.217: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.217: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.217: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.217: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.237: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.237: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.258: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.259: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.259: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.259: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.259: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.259: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.279: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.279: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.300: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.301: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.301: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.301: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.301: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.301: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.320: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.320: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.342: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.342: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.343: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.343: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.343: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.343: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.366: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.366: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.388: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.388: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.388: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.388: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.388: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.389: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.408: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.408: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.430: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.430: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.430: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.430: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.430: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.430: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.451: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.451: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.472: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.473: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.473: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.473: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.473: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.473: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.493: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.493: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.515: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.515: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.516: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.516: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.516: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.516: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.535: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.535: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.557: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.557: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.558: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.558: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.558: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.558: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.578: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.578: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.600: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.600: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.600: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.600: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.600: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.600: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.622: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.622: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.645: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.645: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.645: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.646: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.646: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.646: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.664: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.665: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.686: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.686: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.686: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.686: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.686: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.686: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.705: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.705: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.726: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.726: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.726: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.726: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.727: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.727: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.746: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.746: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.768: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.768: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.769: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.769: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.769: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.769: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.789: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.789: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.812: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.812: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.813: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.813: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.813: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.813: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.833: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.833: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.855: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.855: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.855: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.855: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.855: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.855: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.876: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.877: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.898: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.898: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.899: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.899: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.899: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.899: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.918: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.918: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.939: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.940: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.940: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.940: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.940: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.940: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:39.961: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.961: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.983: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:39.983: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:39.984: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:39.984: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:39.984: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:39.984: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.006: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.006: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.028: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.028: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.028: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.028: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.029: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.029: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.049: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.049: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.071: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.071: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.072: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.072: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.072: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.072: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.091: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.092: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.114: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.114: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.114: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.114: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.114: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.114: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.135: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.135: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.157: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.157: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.157: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.157: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.157: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.157: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.176: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.177: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.201: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.201: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.201: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.201: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.201: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.201: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.221: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.221: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.243: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.243: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.244: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.244: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.244: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.244: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.264: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.264: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.287: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.287: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.287: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.287: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.287: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.287: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.308: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.308: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.329: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.329: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.329: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.329: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.330: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.330: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.350: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.350: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.371: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.371: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.371: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.371: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.371: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.371: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.399: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.399: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.434: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.434: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.434: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.434: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.435: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.435: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.463: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.463: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.498: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.498: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.498: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.498: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.498: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.498: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.526: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.527: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.564: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.565: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.565: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.565: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.565: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.565: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.589: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.589: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.625: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.625: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.625: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.625: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.625: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.625: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.654: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.654: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.684: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.685: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.685: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.685: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.685: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.685: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.717: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.717: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.744: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.744: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.745: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.745: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.745: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.745: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.773: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.773: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.812: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.812: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.812: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.812: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.812: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.812: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.837: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.837: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.871: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.872: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.872: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.872: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.872: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.872: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.899: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.900: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.937: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:40.937: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:40.937: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:40.937: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:40.937: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.937: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:40.969: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:40.969: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.002: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.002: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.002: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.002: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.002: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.002: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.030: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.030: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.062: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.062: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.062: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.063: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.063: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.063: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.099: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.099: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.130: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.130: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.130: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.130: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:41.131: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.131: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:41.161: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.161: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:41.195: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:41.195: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.195: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:41.226: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.226: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:41.262: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:41.262: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.263: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:41.289: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.290: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:41.331: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.331: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.331: variance_after = 20
(process:17874): libfprint-SSM-DEBUG: 04:24:41.331: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.331: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.331: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.363: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.363: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.396: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.396: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.396: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.397: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.397: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.397: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.431: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.431: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.465: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.465: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.465: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.465: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.465: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.465: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.502: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.503: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.540: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.540: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.540: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.540: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.540: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.540: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.571: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.571: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.609: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.609: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.609: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.609: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.609: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.609: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.640: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.640: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.676: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.677: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.677: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.677: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.677: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.677: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.708: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.708: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.737: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.737: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.737: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.737: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.737: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.737: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.763: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.764: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.796: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.796: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.796: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.796: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.796: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.796: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.826: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.826: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.858: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.858: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.858: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.858: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.858: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.859: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.880: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.881: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.916: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.916: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.916: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.916: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.916: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.917: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.941: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.942: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.970: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:41.970: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:41.970: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:41.970: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:41.970: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.970: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:41.996: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:41.996: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.032: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.032: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.032: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.032: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.032: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.032: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.060: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.060: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.092: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.092: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.092: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.092: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.092: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.092: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.125: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.125: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.164: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.164: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.164: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.164: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.165: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.165: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.201: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.201: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.234: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.235: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.235: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.235: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.235: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.235: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.270: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.270: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.300: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.300: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.300: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.300: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.300: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.300: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.335: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.335: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.372: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.372: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.372: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.372: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.372: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.372: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.398: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.399: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.431: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.431: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.431: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.431: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.431: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.431: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.457: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.458: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.494: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.495: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.495: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.495: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.495: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.495: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.521: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.522: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.555: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.555: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.555: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.556: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.556: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.556: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.583: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.583: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.611: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.611: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.611: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.611: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.611: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.611: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.638: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.638: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.670: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.670: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.671: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.671: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.671: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.671: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.704: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.704: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.729: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.729: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.729: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.729: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.729: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.729: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.760: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.760: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.790: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.790: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.790: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.790: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.790: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.790: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.817: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.817: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.849: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.850: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.850: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.850: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.850: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.850: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.881: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.881: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.909: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.909: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.909: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.910: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.910: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.910: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.936: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.936: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.965: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:42.965: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:42.965: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:42.965: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:42.965: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.965: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:42.996: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:42.996: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.025: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.025: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.025: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.025: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.025: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.025: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.052: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.052: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.089: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.089: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.089: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.089: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.089: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.089: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.112: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.112: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.150: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.150: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.150: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.150: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.150: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.150: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.173: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.173: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.206: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.206: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.206: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.206: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.207: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.207: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.233: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.233: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.269: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.269: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.269: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.269: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.270: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.270: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.296: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.296: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.325: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.325: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.325: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.325: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.325: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.325: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.358: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.358: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.388: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.388: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.388: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.388: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.388: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.389: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.418: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.419: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.450: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.450: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.450: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.450: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.451: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.451: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.477: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.477: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.505: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.505: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.505: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.505: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.505: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.505: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.532: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.532: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.565: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.565: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.565: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.565: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.565: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.565: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.592: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.592: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.625: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.625: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.625: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.625: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.625: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.625: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.652: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.652: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.681: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.681: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.681: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.681: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.681: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.682: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.708: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.708: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.740: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.740: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.740: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.740: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.740: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.740: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.766: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.766: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.798: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.798: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.798: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.798: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.799: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.799: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.825: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.825: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.853: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.853: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.853: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.853: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.853: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.853: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.879: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.879: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.907: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.907: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.908: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.908: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.908: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.908: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.942: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.942: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.970: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:43.970: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:43.970: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:43.970: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:43.971: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.971: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:43.996: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:43.996: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.024: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.024: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.024: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.024: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.024: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.024: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.054: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.054: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.082: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.082: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.082: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.082: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.082: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.083: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.109: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.109: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.137: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.137: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.137: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.137: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.138: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.138: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.168: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.168: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.196: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.196: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.196: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.196: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.196: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.196: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.225: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.225: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.257: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.257: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.257: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.257: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.257: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.257: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.287: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.287: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.319: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.319: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.319: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.319: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.319: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.319: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.344: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.344: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.380: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.380: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.380: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.380: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.380: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.380: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.410: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.410: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.442: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.442: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.442: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.442: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.443: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.443: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.469: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.469: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.497: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.497: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.497: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.497: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.497: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.497: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.523: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.523: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.559: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.559: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.559: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.559: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.559: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.559: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.582: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.582: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.615: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.615: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.615: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.615: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.615: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.615: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.642: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.642: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.670: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.670: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.670: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.670: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.670: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.670: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.695: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.695: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.721: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.721: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.721: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.721: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.721: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.721: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.755: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.755: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.780: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.780: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.780: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.780: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.780: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.780: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.815: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.815: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.843: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.843: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.843: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.843: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.843: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.843: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.877: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.877: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.906: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.906: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.906: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.906: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.906: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.906: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.936: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.936: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.971: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:44.971: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:44.972: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:44.972: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:44.972: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.972: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:44.997: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:44.997: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.032: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.033: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.033: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.033: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.033: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.033: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.066: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.066: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.099: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.099: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.099: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.099: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:45.099: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.100: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:45.125: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.125: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:45.156: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:45.156: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.156: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:45.182: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.182: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:45.217: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:45.218: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.218: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:45.243: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.243: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:45.275: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.275: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.275: variance_after = 18
(process:17874): libfprint-SSM-DEBUG: 04:24:45.275: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.275: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.275: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.305: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.305: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.332: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.333: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.333: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.333: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.333: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.333: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.359: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.359: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.395: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.395: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.395: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.395: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.395: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.396: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.422: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.422: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.450: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.450: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.450: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.450: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.450: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.450: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.476: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.476: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.505: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.505: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.505: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.506: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.506: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.506: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.533: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.534: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.561: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.561: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.561: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.561: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.561: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.561: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.601: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.601: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.637: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.637: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.637: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.637: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.638: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.638: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.671: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.671: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.700: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.700: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.700: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.700: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.700: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.700: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.729: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.730: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.765: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.765: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.765: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.765: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.766: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.766: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.795: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.795: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.823: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.823: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.823: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.823: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.823: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.823: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.849: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.849: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.881: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.881: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.881: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.881: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.881: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.881: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.900: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.900: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.921: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.921: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.922: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.922: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.922: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.922: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.940: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.940: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.960: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:45.960: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:45.960: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:45.961: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:45.961: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.961: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:45.979: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:45.980: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.000: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.000: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.000: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.000: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.000: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.001: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.019: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.019: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.039: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.039: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.039: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.040: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.040: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.040: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.058: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.059: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.080: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.080: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.080: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.080: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.080: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.080: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.102: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.102: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.122: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.122: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.122: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.122: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.122: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.122: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.141: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.141: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.162: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.162: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.162: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.162: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.162: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.162: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.180: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.180: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.201: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.201: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.201: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.201: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.201: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.201: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.220: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.220: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.240: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.240: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.240: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.240: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.240: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.240: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.258: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.258: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.279: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.280: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.280: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.280: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.280: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.280: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.298: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.298: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.319: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.319: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.319: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.319: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.319: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.319: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.339: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.339: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.360: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.360: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.360: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.360: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.360: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.360: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.378: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.379: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.399: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.399: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.399: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.399: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.400: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.400: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.418: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.418: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.441: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.441: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.441: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.441: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.441: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.441: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.460: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.460: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.481: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.481: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.481: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.481: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.481: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.481: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.499: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.499: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.520: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.520: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.521: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.521: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.521: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.521: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.539: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.540: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.560: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.560: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.560: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.561: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.561: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.561: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.580: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.580: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.603: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.603: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.603: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.603: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.603: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.603: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.621: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.621: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.641: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.641: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.641: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.641: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.641: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.641: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.659: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.659: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.679: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.679: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.679: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.679: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.679: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.679: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.697: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.697: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.717: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.717: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.717: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.717: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.717: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.717: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.735: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.735: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.756: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.756: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.756: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.756: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.756: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.756: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.778: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.778: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.797: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.798: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.798: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.798: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.798: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.798: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.815: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.816: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.836: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.836: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.836: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.836: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.836: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.836: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.854: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.854: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.874: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.874: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.874: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.875: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.875: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.875: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.893: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.893: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.913: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.913: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.913: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.913: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.913: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.913: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.932: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.932: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.952: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.952: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.952: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.952: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.952: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.952: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:46.969: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.969: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.989: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:46.989: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:46.989: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:46.989: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:46.989: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:46.989: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.008: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.008: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.028: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.028: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.028: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.028: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.028: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.028: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.046: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.046: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.066: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.066: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.066: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.066: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.066: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.067: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.084: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.084: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.105: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.105: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.105: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.105: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.105: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.105: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.125: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.125: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.145: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.145: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.145: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.146: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.146: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.146: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.163: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.163: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.183: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.183: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.183: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.183: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.183: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.183: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.201: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.201: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.221: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.221: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.221: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.221: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.221: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.221: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.239: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.239: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.259: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.260: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.260: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.260: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.260: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.260: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.278: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.278: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.298: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.298: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.298: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.298: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.298: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.299: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.317: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.318: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.338: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.338: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.338: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.339: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.339: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.339: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.356: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.356: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.377: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.377: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.377: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.377: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.377: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.377: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.396: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.396: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.417: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.417: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.418: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.418: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.418: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.418: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.436: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.436: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.457: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.457: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.457: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.457: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.457: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.457: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.476: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.476: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.497: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.497: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.497: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.497: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.497: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.497: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.516: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.516: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.537: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.537: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.538: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.538: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.538: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.538: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.558: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.558: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.578: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.578: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.578: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.578: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.578: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.578: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.596: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.596: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.624: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.624: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.624: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.624: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.624: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.624: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.649: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.649: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.677: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.677: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.678: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.678: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.678: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.678: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.711: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.711: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.739: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.739: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.739: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.739: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.740: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.740: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.767: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.767: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.796: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.796: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.796: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.797: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.797: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.797: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.828: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.828: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.857: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.857: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.857: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.857: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.857: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.857: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.883: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.884: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.918: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.918: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.918: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.918: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.918: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.918: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:47.945: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.945: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.973: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:47.973: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:47.973: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:47.973: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:47.973: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:47.973: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.000: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.000: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.034: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.034: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.034: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.034: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.034: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.034: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.060: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.060: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.089: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.089: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.089: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.089: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.089: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.089: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.119: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.119: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.151: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.151: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.151: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.151: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.151: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.151: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.177: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.177: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.204: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.205: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.205: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.205: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.205: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.205: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.235: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.235: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.262: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.262: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.262: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.262: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.262: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.263: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.288: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.288: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.315: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.316: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.316: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.316: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.316: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.316: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.341: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.341: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.373: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.373: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.373: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.373: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.373: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.373: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.399: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.399: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.430: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.431: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.431: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.431: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.431: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.431: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.456: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.457: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.484: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.484: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.484: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.484: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.484: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.484: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.510: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.510: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.538: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.546: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.546: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.546: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.546: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.546: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.568: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.568: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.595: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.595: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.595: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.595: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.595: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.596: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.621: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.621: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.653: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.653: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.653: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.653: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.653: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.653: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.679: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.679: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.706: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.710: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.710: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.710: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.710: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.710: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.736: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.736: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.767: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.767: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.767: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.767: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.767: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.768: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.789: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.789: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.820: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.821: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.821: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.821: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.821: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.821: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.846: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.847: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.878: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.878: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.878: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.878: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.879: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.879: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.904: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.904: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.936: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.936: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.936: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.936: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.936: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.936: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:48.961: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.961: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.987: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:48.987: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:48.987: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:48.987: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:48.987: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:48.987: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.012: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.012: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.047: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.048: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.048: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.048: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.048: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.048: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.073: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.073: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.101: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.101: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.101: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.101: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.102: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.102: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.128: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.128: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.155: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.155: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.155: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.155: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.155: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.155: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.181: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.181: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.212: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.212: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.212: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.212: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.212: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.213: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.240: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.240: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.274: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.274: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.274: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.274: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.274: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.274: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.301: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.301: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.334: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.334: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.334: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.334: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.334: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.335: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.361: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.361: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.390: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.390: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.390: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.390: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.391: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.391: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.426: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.427: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.451: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.451: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.452: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.452: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.452: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.452: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.478: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.486: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.511: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.511: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.511: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.511: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.511: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.511: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.542: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.542: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.571: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.571: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.571: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.571: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.571: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.571: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.598: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.598: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.633: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.633: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.633: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.633: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.633: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.633: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.665: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.665: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.695: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.695: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.695: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.695: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.696: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.696: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.728: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.728: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.758: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.759: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.759: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.759: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.759: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.759: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.791: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.791: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.821: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.822: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.822: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.822: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.822: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.822: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.850: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.850: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.872: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.872: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.873: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.873: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.873: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.873: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.894: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.894: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.921: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.921: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.921: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.921: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.921: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.921: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:49.949: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.949: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.986: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:49.986: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:49.987: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:49.987: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:49.987: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:49.987: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.014: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.014: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.043: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.043: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.043: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.043: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.043: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.043: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.079: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.079: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.101: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.101: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.101: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.101: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.101: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.101: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.121: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.121: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.142: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.142: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.142: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.143: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.143: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.143: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.162: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.162: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.183: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.183: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.183: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.183: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.183: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.184: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.203: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.203: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.225: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.225: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.225: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.225: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.225: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.225: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.245: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.245: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.267: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.267: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.267: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.267: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.267: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.267: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.287: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.287: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.310: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.310: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.310: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.310: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.310: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.310: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.331: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.332: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.353: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.353: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.353: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.354: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.354: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.354: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.374: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.374: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.396: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.396: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.396: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.396: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.396: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.396: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.416: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.416: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.437: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.437: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.438: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.438: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.438: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.438: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.457: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.457: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.478: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.479: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.479: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.479: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.479: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.479: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.498: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.498: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.522: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.522: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.522: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.522: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.522: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.522: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.541: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.541: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.562: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.562: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.562: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.562: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.562: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.563: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.585: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.585: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.606: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.606: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.607: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.607: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.607: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.607: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.626: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.626: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.647: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.647: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.647: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.647: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.647: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.648: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.666: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.666: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.690: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.690: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.690: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.690: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.690: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.690: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.709: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.709: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.731: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.731: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.731: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.731: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.731: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.732: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.751: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.751: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.773: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.773: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.773: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.773: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.773: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.773: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.792: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.792: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.816: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.816: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.816: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.816: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.817: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.817: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.836: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.836: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.857: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.857: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.857: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.857: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.857: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.858: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.877: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.877: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.899: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.899: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.899: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.899: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.899: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.899: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.919: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.919: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.941: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.941: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.941: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.941: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.942: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.942: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:50.962: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.962: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.983: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:50.983: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:50.983: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:50.983: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:50.984: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:50.984: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.003: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.003: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.026: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.026: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.026: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.026: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.026: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.027: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.047: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.047: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.070: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.070: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.070: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.070: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.070: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.070: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.092: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.092: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.115: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.115: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.115: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.115: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.115: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.115: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.136: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.136: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.158: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.158: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.158: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.158: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.159: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.159: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.179: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.179: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.201: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.201: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.201: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.201: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.201: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.202: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.221: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.221: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.243: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.243: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.243: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.243: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.243: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.243: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.263: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.263: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.285: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.285: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.285: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.285: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.285: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.285: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.305: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.305: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.327: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.327: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.327: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.327: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.327: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.327: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.346: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.347: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.368: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.368: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.368: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.368: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.368: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.368: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.388: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.388: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.409: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.410: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.410: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.410: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.410: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.410: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.429: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.430: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.451: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.451: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.451: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.451: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.451: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.452: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.470: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.470: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.491: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.491: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.491: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.491: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.491: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.491: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.510: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.510: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.531: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.531: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.531: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.531: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.531: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.531: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.549: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.550: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.570: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.570: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.571: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.571: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.571: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.571: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.592: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.592: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.612: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.612: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.612: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.612: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.612: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.612: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.630: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.630: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.650: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.651: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.651: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.651: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.651: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.651: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.669: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.669: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.689: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.689: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.689: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.689: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.689: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.689: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.708: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.708: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.730: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.730: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.730: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.730: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.730: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.730: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.749: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.750: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.772: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.772: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.773: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.773: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.773: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.773: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.794: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.794: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.819: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.819: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.819: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.819: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.819: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.820: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.839: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.839: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.861: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.861: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.861: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.862: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.862: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.862: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.882: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.882: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.903: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.903: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.904: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.904: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.904: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.904: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.925: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.925: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.947: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.948: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.948: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.948: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.948: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.948: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:51.968: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.968: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.989: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:51.990: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:51.990: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:51.990: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:51.990: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:51.990: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.010: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.010: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.032: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.032: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.032: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.032: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.032: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.032: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.053: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.053: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.075: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.075: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.075: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.075: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.075: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.075: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.094: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.094: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.115: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.116: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.116: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.116: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.116: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.116: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.136: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.136: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.157: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.157: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.157: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.158: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.158: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.158: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.177: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.177: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.202: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.202: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.202: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.202: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.202: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.202: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.221: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.221: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.243: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.243: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.243: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.243: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.243: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.243: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.264: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.264: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.286: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.286: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.286: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.286: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.286: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.286: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.305: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.305: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.326: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.327: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.327: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.327: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.327: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.327: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.346: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.346: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.367: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.368: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.368: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.368: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.368: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.368: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.387: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.387: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.409: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.409: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.410: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.410: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.410: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.410: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.429: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.429: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.451: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.451: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.451: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.451: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.451: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.451: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.470: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.470: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.508: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.508: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.508: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.508: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.508: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.508: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.528: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.528: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.549: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.549: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.549: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.549: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.550: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.550: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.569: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.569: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.591: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.591: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.591: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.591: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.591: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.592: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.611: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.611: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.633: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.633: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.633: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.633: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.633: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.634: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.653: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.654: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.675: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.675: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.675: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.675: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.675: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.675: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.694: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.694: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.717: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.717: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.717: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.717: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.717: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.718: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.738: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.738: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.763: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.764: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.764: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.764: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.764: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.764: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.784: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.784: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.807: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.807: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.807: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.807: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.807: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.807: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.827: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.827: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.849: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.849: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.849: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.849: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.849: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.850: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.870: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.870: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.893: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.893: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.893: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.893: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.893: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.893: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.913: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.913: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.936: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.936: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.936: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.936: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.936: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.936: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.956: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.956: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.977: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:52.978: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:52.978: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:52.978: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:52.978: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.978: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:52.998: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:52.998: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.019: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.020: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.020: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.020: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.020: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.020: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.040: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.041: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.063: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.063: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.063: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.063: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.063: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.063: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.083: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.083: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.106: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.106: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.107: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.107: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.107: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.107: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.127: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.127: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.149: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.150: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.150: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.150: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.150: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.150: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.169: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.169: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.191: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.192: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.192: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.192: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.192: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.192: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.212: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.212: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.234: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.235: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.235: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.235: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.235: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.235: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.255: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.255: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.278: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.278: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.278: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.278: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.278: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.278: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.299: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.299: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.321: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.321: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.321: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.321: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.321: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.321: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.342: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.342: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.363: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.363: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.363: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.363: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:53.363: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.363: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:53.384: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.384: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:53.407: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:53.407: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.407: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:53.427: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.427: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:53.449: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:53.449: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.450: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:53.470: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.470: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:53.496: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.496: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.496: variance_after = 20
(process:17874): libfprint-SSM-DEBUG: 04:24:53.496: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.496: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.496: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.516: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.516: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.539: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.539: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.539: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.539: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.540: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.540: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.560: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.560: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.583: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.584: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.584: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.584: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.584: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.584: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.603: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.603: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.625: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.625: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.625: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.625: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.625: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.625: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.644: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.644: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.665: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.666: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.666: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.666: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.666: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.666: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.686: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.686: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.707: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.707: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.707: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.708: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.708: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.708: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.727: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.727: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.749: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.749: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.749: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.749: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.749: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.750: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.769: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.769: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.791: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.791: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.791: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.791: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.791: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.791: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.810: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.810: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.832: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.832: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.832: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.832: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.832: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.832: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.853: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.853: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.875: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.875: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.875: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.875: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.875: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.875: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.895: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.896: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.918: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.918: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.918: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.918: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.918: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.918: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.939: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.939: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.961: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:53.961: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:53.962: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:53.962: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:53.962: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.962: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:53.983: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:53.983: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.005: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.005: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.006: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.006: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.006: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.006: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.026: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.026: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.048: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.048: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.048: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.048: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.048: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.049: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.068: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.068: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.091: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.091: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.091: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.091: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.091: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.091: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.111: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.111: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.135: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.135: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.136: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.136: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.136: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.136: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.156: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.156: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.179: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.179: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.179: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.180: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.180: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.180: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.200: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.200: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.222: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.222: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.222: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.222: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.222: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.222: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.241: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.241: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.263: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.263: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.263: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.263: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.264: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.264: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.283: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.283: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.304: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.304: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.304: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.304: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.304: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.304: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.324: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.324: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.346: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.346: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.346: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.346: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.346: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.346: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.365: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.366: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.387: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.387: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.387: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.387: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.387: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.387: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.406: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.407: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.428: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.429: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.429: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.429: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.429: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.429: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.448: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.448: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.469: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.469: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.469: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.469: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.469: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.469: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.487: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.487: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.509: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.509: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.509: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.509: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.509: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.509: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.535: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.535: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.563: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.563: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.563: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.563: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.563: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.563: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.593: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.593: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.620: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.620: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.620: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.620: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.621: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.621: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.650: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.650: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.682: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.682: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.682: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.682: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.682: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.682: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.707: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.707: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.743: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.743: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.743: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.743: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.743: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.743: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.768: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.768: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.796: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.796: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.796: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.796: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.796: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.796: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.821: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.821: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.849: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.849: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.849: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.849: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.849: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.849: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.878: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.878: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.906: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.906: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.906: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.906: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.906: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.906: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.933: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.933: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.964: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:54.964: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:54.964: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:54.964: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:54.964: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.964: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:54.990: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:54.990: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.021: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.021: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.022: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.022: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.022: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.022: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.047: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.047: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.083: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.083: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.083: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.083: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.083: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.083: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.104: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.105: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.140: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.140: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.140: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.140: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.141: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.141: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.166: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.166: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.194: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.194: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.194: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.194: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.194: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.194: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.224: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.224: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.253: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.254: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.254: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.254: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.254: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.254: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.287: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.287: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.321: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.321: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.322: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.322: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.322: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.322: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.349: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.349: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.383: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.383: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.383: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.384: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.384: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.384: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.419: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.419: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.449: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.449: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.449: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.449: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.449: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.450: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.481: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.481: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.510: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.510: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.510: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.511: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.511: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.511: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.546: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.546: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.575: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.576: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.576: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.576: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.576: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.576: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.603: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.603: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.632: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.632: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.633: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.633: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.633: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.633: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.667: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.668: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.705: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.705: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.705: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.705: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.705: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.706: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.729: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.729: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.766: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.766: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.766: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.766: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.766: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.766: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.793: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.793: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.827: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.827: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.827: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.827: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.827: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.827: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.858: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.858: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.887: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.887: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.887: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.887: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.887: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.887: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.918: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.919: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.948: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:55.948: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:55.948: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:55.948: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:55.948: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.948: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:55.979: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:55.979: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.009: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.009: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.009: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.009: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.009: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.009: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.040: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.041: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.074: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.074: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.074: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.074: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.074: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.074: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.101: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.101: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.138: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.139: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.139: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.139: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.139: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.139: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.166: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.166: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.195: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.195: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.195: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.195: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.195: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.195: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.226: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.226: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.259: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.260: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.260: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.260: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.260: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.260: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.286: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.287: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.313: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.313: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.313: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.313: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:56.314: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.314: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:56.340: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.340: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:56.377: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:56.377: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.377: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:56.404: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.404: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:56.437: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:56.438: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.438: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:56.465: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.465: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:56.502: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.503: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.503: variance_after = 18
(process:17874): libfprint-SSM-DEBUG: 04:24:56.503: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.503: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.503: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.530: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.530: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.560: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.560: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.560: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.560: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.560: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.560: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.587: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.587: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.621: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.621: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.621: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.621: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.621: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.621: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.652: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.653: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.686: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.686: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.686: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.686: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.686: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.686: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.714: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.714: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.747: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.747: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.747: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.747: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.748: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.748: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.779: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.779: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.808: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.808: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.808: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.809: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.809: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.809: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.840: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.840: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.873: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.873: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.874: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.874: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.874: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.874: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.901: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.901: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.938: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:56.939: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:56.939: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:56.939: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:56.939: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.939: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:56.966: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:56.966: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.000: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.000: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.000: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.000: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.000: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.000: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.032: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.032: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.065: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.065: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.065: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.065: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.065: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.065: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.096: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.096: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.129: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.129: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.129: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.129: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.130: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.130: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.160: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.161: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.198: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.198: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.198: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.199: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.199: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.199: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.229: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.230: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.267: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.267: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.267: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.267: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.267: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.267: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.302: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.302: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.344: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.344: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.344: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.344: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.344: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.344: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.373: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.373: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.416: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.416: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.416: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.417: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.417: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.417: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.449: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.449: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.484: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.484: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.484: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.484: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.485: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.485: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.518: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.519: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.554: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.554: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.554: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.554: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.554: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.554: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.587: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.587: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.624: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.624: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.624: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.624: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.625: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.625: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.686: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.686: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.723: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.723: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.723: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.723: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.724: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.724: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.762: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.762: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.806: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.806: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.806: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.806: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.806: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.806: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.832: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.832: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.854: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.854: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.854: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.855: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.855: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.855: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.873: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.873: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.894: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.894: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.894: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.894: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.894: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.894: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.912: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.912: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.932: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.932: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.932: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.932: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.932: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.932: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.950: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.950: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.970: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:57.970: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:57.971: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:57.971: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:57.971: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.971: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:57.989: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:57.989: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.009: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.009: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.009: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.009: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.009: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.009: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.027: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.028: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.048: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.048: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.048: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.048: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.048: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.048: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.066: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.067: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.087: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.087: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.087: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.087: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.087: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.088: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.106: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.106: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.126: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.126: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.126: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.126: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.127: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.127: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.145: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.145: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.171: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.171: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.171: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.172: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.172: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.172: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.191: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.192: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.213: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.213: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.213: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.213: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.213: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.213: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.233: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.233: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.255: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.255: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.255: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.255: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.255: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.255: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.275: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.275: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.297: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.297: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.297: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.297: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.297: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.297: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.317: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.317: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.339: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.339: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.339: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.339: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.339: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.339: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.360: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.360: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.382: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.382: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.382: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.382: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.382: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.382: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.401: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.402: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.423: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.423: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.423: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.423: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.423: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.424: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.443: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.443: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.465: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.465: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.465: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.465: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.465: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.465: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.485: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.485: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.506: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.507: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.507: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.507: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.507: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.507: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.526: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.526: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.548: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.548: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.549: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.549: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.549: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.549: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.568: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.568: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.590: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.590: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.590: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.590: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.590: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.590: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.610: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.610: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.631: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.632: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.632: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.632: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.632: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.632: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.652: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.653: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.683: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.683: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.683: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.683: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.683: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.683: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.713: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.713: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.743: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.743: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.743: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.743: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.743: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.743: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.770: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.770: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.803: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.803: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.803: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.803: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.803: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.803: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:58.862: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.862: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.926: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:58.926: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:58.926: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:58.926: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:58.927: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:58.927: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.170: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.170: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.263: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.263: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.263: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.264: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.264: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.264: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.291: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.291: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.319: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.320: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.320: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.320: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.320: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.320: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.339: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.339: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.360: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.361: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.361: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.361: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.361: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.361: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.380: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.380: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.401: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.402: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.402: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.402: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.402: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.402: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.421: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.421: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.442: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.442: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.442: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.442: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.442: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.442: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.461: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.461: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.483: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.483: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.483: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.483: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.483: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.483: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.502: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.502: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.523: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.524: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.524: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.524: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.524: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.524: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.543: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.543: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.564: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.564: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.564: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.565: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.565: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.565: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.584: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.584: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.606: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.606: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.606: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.606: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.606: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.606: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.626: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.626: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.647: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.647: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.648: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.648: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.648: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.648: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.667: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.667: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.688: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.688: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.689: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.689: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.689: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.689: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.708: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.708: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.728: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.728: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.728: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.728: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:59.728: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.728: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:59.757: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.757: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:59.787: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:59.788: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.788: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:59.807: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.807: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:59.828: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:24:59.828: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.828: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:24:59.864: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.864: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:24:59.894: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.902: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.903: variance_after = 18
(process:17874): libfprint-SSM-DEBUG: 04:24:59.903: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.903: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.903: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:24:59.925: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.926: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.967: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:24:59.967: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:24:59.967: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:24:59.967: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:24:59.967: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:24:59.967: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.002: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.002: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.032: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.032: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.033: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.033: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.033: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.033: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.069: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.069: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.106: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.106: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.106: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.106: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.107: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.107: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.138: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.138: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.171: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.171: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.171: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.171: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.171: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.171: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.197: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.198: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.235: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.235: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.235: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.235: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.235: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.235: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.266: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.266: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.295: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.295: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.295: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.295: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.295: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.295: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.327: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.327: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.356: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.356: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.356: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.356: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.356: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.356: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.387: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.387: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.420: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.420: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.420: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.420: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.421: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.421: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.448: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.448: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.481: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.481: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.481: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.481: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.481: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.481: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.558: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.558: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.581: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.581: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.581: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.581: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.581: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.581: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.616: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.616: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.653: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.654: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.654: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.654: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.654: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.654: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.689: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.689: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.726: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.726: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.726: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.726: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.726: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.727: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.760: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.760: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.796: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.796: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.796: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.796: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.796: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.796: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.823: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.823: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.859: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.859: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.859: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.859: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.859: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.859: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.892: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.892: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.920: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.921: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.921: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.921: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.921: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.921: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:00.952: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.952: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.987: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:00.987: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:00.988: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:00.988: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:00.988: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:00.988: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.014: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.014: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.046: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.046: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.046: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.047: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.047: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.047: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.073: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.073: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.110: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.110: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.110: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.110: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.110: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.110: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.141: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.141: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.173: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.174: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.174: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.174: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.174: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.174: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.208: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.209: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.240: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.240: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.240: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.240: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.240: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.240: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.269: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.270: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.301: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.301: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.301: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.301: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.301: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.301: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.331: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.331: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.363: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.364: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.364: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.364: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.364: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.364: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.390: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.390: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.423: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.423: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.423: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.423: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.423: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.423: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.457: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.457: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.497: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.497: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.498: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.498: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.498: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.498: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.531: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.531: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.564: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.564: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.564: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.564: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.564: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.564: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.598: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.599: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.631: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.631: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.631: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.631: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.631: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.631: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.667: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.667: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.702: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.702: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.702: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.702: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.702: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.702: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.732: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.732: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.769: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.769: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.769: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.769: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.769: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.769: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.795: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.795: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.832: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.832: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.832: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.832: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.832: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.832: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.866: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.866: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.890: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.894: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.894: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.894: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.894: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.894: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.920: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.921: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.949: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:01.949: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:01.949: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:01.949: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:01.949: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.949: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:01.990: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:01.990: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.030: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.030: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.031: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.031: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.031: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.031: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.058: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.067: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.096: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.096: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.096: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.096: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.096: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.096: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.131: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.132: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.206: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.206: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.206: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.206: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.206: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.206: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.259: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.259: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.332: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.333: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.333: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.333: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.333: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.333: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.390: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.390: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.453: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.453: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.453: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.453: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.453: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.453: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.525: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.525: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.540: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.540: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.540: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.540: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.540: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.541: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.559: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.559: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.581: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.582: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.582: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.582: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.582: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.582: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.601: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.601: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.621: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.621: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.621: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.621: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.621: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.621: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.641: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.641: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.661: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.662: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.662: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.662: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.662: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.662: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.682: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.682: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.704: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.704: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.704: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.704: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.704: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.704: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.724: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.724: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.745: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.745: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.745: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.745: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.745: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.746: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.764: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.765: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.785: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.785: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.785: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.785: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.786: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.786: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.804: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.804: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.825: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.825: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.825: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.825: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.826: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.826: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.845: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.845: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.866: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.866: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.866: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.866: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.866: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.866: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.885: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.885: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.907: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.907: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.907: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.907: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.907: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.907: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.926: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.926: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.947: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.947: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.948: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.948: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.948: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.948: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:02.967: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.967: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.989: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:02.989: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:02.989: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:02.990: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:02.990: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:02.990: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.011: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.011: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.035: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.035: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.036: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.036: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.036: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.036: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.065: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.065: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.107: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.107: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.107: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.107: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.107: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.107: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.136: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.136: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.179: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.179: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.179: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.179: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.179: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.179: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.208: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.208: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.243: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.243: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.244: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.244: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.244: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.244: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.270: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.270: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.308: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.308: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.308: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.308: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.308: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.308: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.351: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.351: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.398: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.398: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.398: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.398: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.399: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.399: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.421: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.421: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.462: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.462: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.462: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.462: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.462: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.462: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.485: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.485: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.526: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.526: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.526: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.526: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.526: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.527: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.559: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.559: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.596: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.596: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.596: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.597: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.597: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.597: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.631: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.631: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.660: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.660: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.660: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.660: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.660: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.661: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.695: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.695: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.728: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.728: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.728: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.728: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.729: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.729: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.763: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.763: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.808: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.808: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.808: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.808: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.808: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.808: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.839: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.839: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.875: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.875: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.876: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.876: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.876: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.876: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.903: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.903: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.939: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:03.940: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:03.940: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:03.940: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:03.940: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.940: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:03.972: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:03.972: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.001: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.001: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.001: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.001: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.001: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.001: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.036: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.036: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.075: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.075: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.075: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.076: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.076: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.076: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.105: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.105: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.138: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.138: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.139: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.139: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.139: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.139: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.172: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.172: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.211: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.211: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.211: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.212: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.212: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.212: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.240: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.240: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.275: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.275: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.275: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.275: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.276: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.276: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.309: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.309: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.343: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.343: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.344: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.344: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.344: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.344: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.373: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.373: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.400: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.400: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.400: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.401: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.401: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.401: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.431: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.431: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.467: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.467: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.467: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.467: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.467: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.467: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.492: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.492: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.524: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.525: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.525: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.525: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.525: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.525: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.556: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.556: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.587: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.588: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.588: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.588: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.588: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.588: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.613: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.613: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.644: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.644: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.645: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.645: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.645: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.645: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.682: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.682: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.706: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.706: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.706: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.706: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.706: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.706: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.732: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.732: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.760: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.760: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.760: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.760: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.760: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.760: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.790: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.790: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.823: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.823: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.823: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.823: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.823: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.823: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.849: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.849: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.885: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.885: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.885: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.885: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.885: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.885: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.915: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.915: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.944: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.944: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.944: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.944: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.944: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.944: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:04.962: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.962: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.982: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:04.982: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:04.982: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:04.982: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:04.982: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:04.982: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.003: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.003: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.023: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.024: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.024: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.024: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.024: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.024: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.042: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.042: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.062: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.062: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.062: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.062: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.062: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.062: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.081: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.081: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.101: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.101: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.101: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.101: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.101: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.101: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.120: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.120: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.140: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.140: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.141: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.141: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.141: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.141: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.160: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.160: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.180: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.180: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.180: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.180: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.180: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.180: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.199: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.199: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.219: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.219: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.219: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.219: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.219: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.220: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.239: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.239: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.258: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.259: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.259: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.259: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.259: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.259: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.277: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.277: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.297: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.297: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.298: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.298: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.298: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.298: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.316: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.316: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.337: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.337: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.337: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.337: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.337: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.337: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.375: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.375: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.407: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.407: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.407: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.407: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:05.407: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.407: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:05.442: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.442: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:05.479: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:05.479: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.479: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:05.510: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.510: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:05.539: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:05.539: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.539: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:05.574: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.574: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:05.603: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.603: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.603: variance_after = 18
(process:17874): libfprint-SSM-DEBUG: 04:25:05.603: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.603: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.603: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.634: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.634: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.672: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.672: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.672: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.672: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.672: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.672: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.703: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.703: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.740: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.741: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.741: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.741: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.741: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.741: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.776: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.776: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.805: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.805: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.805: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.805: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.805: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.805: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.840: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.840: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.869: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.869: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.869: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.869: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.869: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.869: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.896: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.896: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.933: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.933: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.934: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.934: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.934: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.934: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:05.961: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.961: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.989: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:05.990: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:05.990: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:05.990: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:05.990: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:05.990: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.021: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.021: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.046: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.046: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.046: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.046: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.046: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.046: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.082: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.082: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.120: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.120: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.120: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.120: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.121: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.121: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.150: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.158: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.184: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.184: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.184: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.184: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.184: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.185: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.230: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.230: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.261: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.261: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.261: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.261: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.261: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.261: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.297: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.297: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.330: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.330: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.330: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.330: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.330: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.330: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.357: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.357: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.390: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.390: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.390: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.390: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.391: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.391: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.417: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.417: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.450: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.451: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.451: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.451: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.451: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.451: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.477: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.478: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.514: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.515: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.515: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.515: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.515: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.515: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.541: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.541: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.576: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.576: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.576: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.576: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.576: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.576: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.603: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.603: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.636: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.636: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.636: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.637: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.637: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.637: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.664: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.665: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.698: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.698: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.698: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.698: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.698: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.698: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.726: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.726: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.760: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.760: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.760: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.760: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.760: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.760: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.787: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.787: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.818: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.818: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.818: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.818: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.818: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.818: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.845: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.846: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.896: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.896: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.896: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.897: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.897: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.897: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.926: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.926: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.955: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:06.955: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:06.956: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:06.956: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:06.956: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.956: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:06.987: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:06.987: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.017: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.017: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.017: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.017: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.017: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.017: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.045: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.045: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.083: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.083: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.083: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.083: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.083: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.083: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.107: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.107: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.137: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.137: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.137: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.137: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.138: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.138: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.169: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.169: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.199: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.199: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.199: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.199: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.199: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.199: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.227: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.227: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.261: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.261: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.261: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.261: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.261: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.261: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.288: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.288: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.318: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.318: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.318: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.318: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.318: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.318: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.350: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.350: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.384: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.384: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.384: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.384: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.384: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.384: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.407: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.407: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.440: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.440: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.440: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.440: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.440: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.440: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.466: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.466: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.503: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.503: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.503: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.503: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.503: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.503: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.530: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.530: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.558: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.559: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.559: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.559: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.559: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.559: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.590: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.590: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.615: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.615: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.615: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.615: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.615: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.615: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.646: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.646: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.675: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.675: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.675: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.675: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.675: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.675: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.702: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.702: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.731: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.731: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.731: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.731: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.731: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.731: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.758: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.758: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.793: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.793: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.793: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.793: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.794: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.794: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.816: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.816: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.849: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.849: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.849: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.849: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.849: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.849: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.875: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.876: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.905: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.905: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.905: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.905: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.905: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.905: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.935: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.936: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.964: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:07.964: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:07.964: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:07.964: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:07.964: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.964: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:07.994: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:07.994: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.023: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.023: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.023: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.023: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.023: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.023: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.053: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.053: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.081: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.081: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.081: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.081: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.082: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.082: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.111: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.111: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.143: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.144: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.144: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.144: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.144: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.144: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.169: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.169: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.197: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.197: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.197: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.197: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.197: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.197: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.227: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.227: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.258: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.258: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.258: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.258: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.258: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.259: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.284: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.284: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.311: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.311: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.311: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.312: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.312: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.312: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.337: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.337: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.372: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.373: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.373: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.373: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.373: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.373: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.399: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.399: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.419: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.419: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.419: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.419: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.419: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.419: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.436: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.437: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.456: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.456: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.456: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.456: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.456: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.456: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.474: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.474: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.494: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.494: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.494: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.494: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.494: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.494: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.512: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.512: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.535: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.536: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.536: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.536: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.536: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.536: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.563: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.563: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.584: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.584: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.584: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.584: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.585: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.585: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.603: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.603: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.623: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.623: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.623: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.623: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.623: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.623: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.642: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.642: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.661: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.662: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.662: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.662: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.662: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.662: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.682: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.682: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.707: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.708: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.708: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.708: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.708: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.708: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.726: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.726: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.746: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.746: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.746: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.746: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.746: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.746: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.764: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.764: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.784: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.785: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.785: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.785: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.785: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.785: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.803: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.804: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.824: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.824: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.824: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.824: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.824: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.824: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.842: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.843: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.863: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.863: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.863: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.863: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.863: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.863: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.881: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.881: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.903: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.903: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.903: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.903: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.904: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.904: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.921: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.921: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.942: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.942: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.942: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.942: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.942: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.942: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:08.960: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.961: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.980: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:08.980: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:08.981: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:08.981: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:08.981: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:08.981: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.011: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.011: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.031: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.031: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.031: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.031: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.031: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.031: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.048: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.048: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.068: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.068: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.068: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.068: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.068: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.068: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.086: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.086: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.105: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.105: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.106: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.106: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.106: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.106: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.133: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.133: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.153: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.153: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.153: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.153: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.153: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.153: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.171: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.171: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.194: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.195: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.195: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.195: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.195: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.195: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.212: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.212: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.231: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.232: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.232: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.232: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.232: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.232: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.249: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.250: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.269: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.269: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.269: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.269: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.269: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.270: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.287: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.287: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.306: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.307: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.307: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.307: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.307: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.307: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.324: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.324: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.344: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.344: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.344: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.344: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.344: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.344: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.361: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.361: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.382: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.382: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.382: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.382: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.382: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.382: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.399: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.399: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.419: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.419: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.419: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.419: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.419: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.419: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.437: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.437: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.456: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.456: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.456: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.456: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.457: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.457: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.474: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.474: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.493: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.493: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.493: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.493: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.493: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.493: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.510: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.510: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.530: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.531: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.531: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.531: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.531: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.531: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.549: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.549: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.570: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.570: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.571: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.571: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.571: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.571: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.589: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.589: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.610: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.610: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.610: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.610: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.610: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.610: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.629: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.629: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.650: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.651: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.651: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.651: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.651: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.651: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.670: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.670: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.696: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.696: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.697: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.697: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.697: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.697: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.714: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.714: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.736: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.736: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.736: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.737: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.737: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.737: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.755: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.755: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.776: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.776: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.776: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.776: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.776: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.776: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.796: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.796: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.817: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.817: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.817: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.817: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.817: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.817: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.836: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.837: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.858: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.859: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.859: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.859: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.859: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.859: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.881: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.881: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.903: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.903: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.903: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.903: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.903: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.903: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.922: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.923: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.943: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.943: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.943: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.944: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.944: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.944: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:09.962: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.962: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.986: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:09.986: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:09.986: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:09.986: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:09.986: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:09.986: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.005: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.005: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.026: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.026: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.026: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.026: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.026: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.026: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.049: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.049: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.076: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.077: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.077: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.077: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.077: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.077: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.096: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.096: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.117: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.118: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.118: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.118: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.118: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.118: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.137: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.137: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.160: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.160: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.160: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.161: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.161: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.161: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.183: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.183: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.203: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.204: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.204: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.204: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.204: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.204: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.225: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.226: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.247: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.247: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.247: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.247: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.247: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.247: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.266: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.266: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.288: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.288: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.288: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.289: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.289: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.289: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.307: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.307: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.328: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.329: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.329: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.329: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.329: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.329: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.348: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.348: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.369: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.369: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.369: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.369: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.369: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.369: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.389: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.389: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.410: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.410: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.410: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.411: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.411: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.411: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.429: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.430: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.451: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.451: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.451: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.451: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.451: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.452: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.470: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.471: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.492: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.492: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.492: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.492: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.492: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.492: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.513: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.513: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.534: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.534: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.535: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.535: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.535: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.535: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.554: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.554: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.576: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.576: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.576: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.576: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.576: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.576: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.597: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.597: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.619: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.619: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.620: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.620: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:10.620: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.620: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:10.641: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.641: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:10.664: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:10.664: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.664: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:10.683: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.683: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:10.705: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:10.705: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.705: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:10.723: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.724: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:10.744: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.744: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.745: variance_after = 18
(process:17874): libfprint-SSM-DEBUG: 04:25:10.745: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.745: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.745: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.769: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.769: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.789: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.789: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.789: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.790: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.790: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.790: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.808: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.808: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.829: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.829: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.829: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.829: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.829: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.829: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.848: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.848: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.869: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.869: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.869: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.869: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.869: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.869: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.888: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.888: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.908: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.908: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.908: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.908: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.908: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.908: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.927: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.927: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.948: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:10.948: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:10.948: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:10.948: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:10.948: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.948: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:10.971: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.971: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:10.999: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.000: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.000: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.000: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.000: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.000: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.019: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.019: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.039: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.039: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.039: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.039: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.039: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.039: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.057: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.057: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.078: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.078: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.078: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.078: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.078: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.078: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.096: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.097: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.117: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.118: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.118: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.118: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.118: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.118: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.137: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.137: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.158: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.158: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.158: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.158: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.158: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.158: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.177: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.177: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.197: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.197: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.197: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.197: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.197: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.197: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.216: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.216: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.245: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.245: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.245: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.245: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.245: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.245: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.279: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.279: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.318: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.318: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.318: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.318: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.318: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.319: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.345: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.345: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.383: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.383: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.383: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.383: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.383: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.383: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.412: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.413: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.432: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.432: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.432: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.433: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.433: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.433: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.452: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.452: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.487: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.487: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.487: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.487: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.488: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.488: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.509: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.509: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.528: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.529: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.529: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.529: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.529: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.529: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.546: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.546: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.566: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.566: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.566: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.566: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.566: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.566: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.587: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.587: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.608: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.609: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.609: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.609: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.609: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.609: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.626: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.626: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.646: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.646: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.646: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.646: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.646: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.646: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.664: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.664: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.686: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.686: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.686: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.686: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.686: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.686: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.707: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.707: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.730: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.730: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.730: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.730: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.730: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.730: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.750: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.750: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.772: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.772: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.772: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.772: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.772: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.773: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.791: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.791: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.812: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.812: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.812: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.812: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.812: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.812: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.831: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.831: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.852: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.852: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.852: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.852: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.852: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.852: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.871: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.871: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.892: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.892: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.892: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.892: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.892: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.893: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.911: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.911: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.932: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.933: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.933: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.933: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.933: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.933: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:11.952: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.952: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.973: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:11.973: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:11.973: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:11.974: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:11.974: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:11.982: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.009: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.009: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.038: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.039: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.039: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.039: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.039: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.039: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.066: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.066: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.100: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.100: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.100: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.100: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.100: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.100: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.128: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.128: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.162: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.162: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.162: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.162: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.162: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.163: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.195: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.195: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.225: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.226: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.226: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.226: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.226: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.226: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.254: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.254: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.287: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.288: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.288: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.288: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.288: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.288: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.316: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.316: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.345: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.346: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.346: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.354: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.354: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.354: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.381: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.381: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.410: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.410: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.410: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.410: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.411: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.411: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.437: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.437: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.471: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.471: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.471: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.471: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.471: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.471: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.502: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.502: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.531: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.531: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.531: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.531: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.531: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.532: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.566: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.567: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.595: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.596: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.596: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.596: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.596: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.596: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.623: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.623: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.652: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.652: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.652: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.652: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.652: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.652: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.681: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.681: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.714: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.715: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.715: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.715: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.715: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.715: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.746: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.746: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.775: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.775: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.775: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.775: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.776: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.776: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.803: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.803: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.836: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.836: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.836: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.836: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:12.836: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.836: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:12.863: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.863: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.894: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:12.894: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.894: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:12.894: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:12.894: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.894: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:12.918: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.918: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:12.948: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:12.948: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:12.948: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:12.978: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:12.978: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:13.007: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:13.007: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.007: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:13.035: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.035: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:13.068: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.069: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.069: variance_after = 17
(process:17874): libfprint-SSM-DEBUG: 04:25:13.069: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.069: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.069: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.096: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.096: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.134: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.134: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.134: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.134: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.134: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.134: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.157: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.157: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.186: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.186: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.186: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.186: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.186: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.186: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.217: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.217: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.246: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.246: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.246: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.246: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.246: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.246: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.273: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.273: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.310: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.310: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.310: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.310: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.310: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.310: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.337: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.337: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.366: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.366: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.366: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.366: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.366: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.366: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.393: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.393: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.430: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.430: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.430: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.430: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.430: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.430: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.456: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.457: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.498: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.498: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.498: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.498: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.498: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.499: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.523: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.523: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.552: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.552: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.552: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.552: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.552: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.552: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.587: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.587: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.615: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.615: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.616: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.616: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.616: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.616: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.642: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.642: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.671: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.671: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.671: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.671: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.671: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.671: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.702: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.702: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.732: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.732: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.732: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.732: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.733: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.733: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.764: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.765: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.798: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.798: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.798: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.798: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.798: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.798: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.826: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.826: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.862: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.862: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.862: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.862: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.862: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.862: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.886: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.886: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.916: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.916: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.916: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.916: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.916: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.916: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:13.948: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.948: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.983: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:13.983: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:13.983: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:13.983: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:13.983: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:13.983: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.011: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.011: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.040: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.040: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.041: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.041: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.041: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.041: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.076: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.076: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.106: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.106: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.106: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.106: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.106: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.107: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.134: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.134: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.163: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.164: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.164: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.164: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.164: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.164: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.199: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.199: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.225: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.225: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.225: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.225: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.225: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.225: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.258: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.258: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.287: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.288: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.288: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.288: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.288: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.288: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.320: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.320: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.350: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.351: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.351: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.351: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.351: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.351: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.383: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.383: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.413: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.413: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.413: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.413: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.413: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.413: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.442: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.442: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.476: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.476: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.476: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.476: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.476: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.476: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.505: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.505: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.539: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.539: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.539: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.539: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.539: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.539: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.570: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.570: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.600: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.600: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.600: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.601: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.601: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.601: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.628: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.629: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.668: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.668: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.668: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.668: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.668: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.668: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.692: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.692: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.726: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.726: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.726: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.727: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.727: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.727: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.750: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.751: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.784: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.785: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.785: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.785: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.785: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.785: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.813: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.813: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.851: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.851: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.851: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.851: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.851: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.851: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.875: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.875: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.909: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.909: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.909: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.909: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.909: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.909: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:14.938: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.938: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.975: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:14.975: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:14.976: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:14.976: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:14.976: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:14.976: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.003: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.003: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.037: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.038: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.042: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.042: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.042: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.042: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.073: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.073: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.103: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.103: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.103: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.103: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.103: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.103: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.134: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.134: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.164: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.164: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.164: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.164: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.164: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.164: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.195: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.196: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.225: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.225: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.225: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.225: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.225: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.225: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.252: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.252: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.290: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.290: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.290: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.290: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.290: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.290: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.318: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.318: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.351: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.351: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.351: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.351: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.351: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.351: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.382: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.382: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.411: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.412: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.412: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.412: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.412: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.412: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.439: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.439: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.472: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.472: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.472: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.472: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.472: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.472: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.503: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.503: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.533: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.533: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.533: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.533: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.533: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.533: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.560: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.560: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.589: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.589: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.589: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.589: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.589: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.589: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.621: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.621: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.655: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.655: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.655: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.655: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.655: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.656: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.684: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.684: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.711: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.711: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.712: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.712: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:15.712: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.712: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:15.744: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.744: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:15.774: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:15.774: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.774: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:15.802: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.802: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:15.835: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:15.835: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.835: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:15.866: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.866: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:15.896: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.896: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.896: variance_after = 16
(process:17874): libfprint-SSM-DEBUG: 04:25:15.896: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.896: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.896: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.923: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.923: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.953: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:15.953: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:15.953: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:15.953: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:15.953: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.953: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:15.981: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:15.981: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.014: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.014: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.014: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.014: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.014: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.014: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.042: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.042: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.080: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.080: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.080: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.080: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.080: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.080: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.104: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.105: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.139: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.139: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.139: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.139: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.140: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.140: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.172: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.172: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.201: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.202: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.202: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.202: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.202: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.202: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.230: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.230: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.267: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.268: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.268: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.268: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.268: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.268: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.295: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.295: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.325: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.325: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.325: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.325: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.325: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.325: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.356: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.356: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.390: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.390: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.390: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.390: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.390: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.390: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.417: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.418: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.455: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.455: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.455: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.455: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.455: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.455: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.479: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.479: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.513: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.513: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.513: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.513: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.513: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.513: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.540: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.541: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.574: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.574: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.574: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.574: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.574: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.574: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.601: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.602: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.635: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.636: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.636: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.636: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.636: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.636: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.668: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.668: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.696: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.696: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.696: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.696: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.696: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.696: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.724: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.724: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.762: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.762: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.762: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.762: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.762: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.762: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.791: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.791: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.821: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.821: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.821: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.821: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.821: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.821: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.854: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.854: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.884: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.884: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.884: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.884: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.884: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.884: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.916: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.917: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.946: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:16.947: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:16.947: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:16.947: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:16.947: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.947: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:16.981: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:16.981: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.011: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.011: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.011: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.011: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.011: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.012: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.039: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.039: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.072: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.072: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.072: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.072: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.073: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.073: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.100: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.100: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.139: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.139: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.139: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.139: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.139: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.139: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.163: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.163: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.201: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.201: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.201: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.201: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.201: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.201: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.225: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.225: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.264: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.264: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.264: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.264: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.264: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.264: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.292: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.292: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.326: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.326: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.326: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.327: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.327: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.327: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.355: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.355: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.384: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.385: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.385: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.385: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.385: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.385: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.417: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.417: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.447: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.447: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.447: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.447: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.447: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.447: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.479: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.480: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.509: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.509: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.509: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.509: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.509: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.509: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.536: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.536: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.571: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.571: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.571: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.571: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.571: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.571: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.598: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.599: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.636: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.636: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.636: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.636: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.636: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.636: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.664: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.664: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.694: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.694: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.694: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.694: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.694: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.694: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.721: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.721: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.758: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.758: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.758: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.758: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.758: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.758: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.784: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.784: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.813: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.813: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.813: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.813: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.813: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.813: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.840: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.840: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.860: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.860: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.860: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.860: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.860: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.860: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.889: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.889: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.916: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.916: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.917: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.917: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.917: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.917: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:17.950: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.951: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.978: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:17.978: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:17.978: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:17.978: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:17.978: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:17.978: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.004: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.004: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.046: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.046: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.046: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.046: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.046: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.047: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.070: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.070: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.097: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.097: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.098: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.098: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.098: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.098: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.127: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.127: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.166: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.166: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.166: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.166: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.166: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.167: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.201: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.201: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.237: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.237: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.237: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.237: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.237: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.237: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.263: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.263: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.295: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.295: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.295: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.295: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.295: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.295: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.321: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.321: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.349: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.349: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.349: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.349: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.349: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.349: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.380: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.380: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.408: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.408: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.408: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.408: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.408: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.408: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.434: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.434: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.461: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.461: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.461: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.461: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.461: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.462: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.488: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.488: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.515: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.516: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.516: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.516: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:18.516: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.516: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:18.547: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.547: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:18.576: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:18.576: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.576: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:18.601: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.602: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:18.629: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:18.629: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.629: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:18.663: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.663: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:18.691: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.691: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.691: variance_after = 17
(process:17874): libfprint-SSM-DEBUG: 04:25:18.691: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.691: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.691: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.717: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.717: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.744: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.744: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.744: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.745: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.745: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.745: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.771: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.771: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.802: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.803: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.803: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.803: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.803: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.803: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.829: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.829: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.856: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.857: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.857: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.857: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.857: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.857: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.887: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.887: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.919: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.919: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.919: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.919: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.919: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.919: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:18.945: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.945: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.973: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:18.973: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:18.973: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:18.973: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:18.974: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:18.974: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.003: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.003: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.031: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.031: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.031: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.031: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.031: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.031: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.057: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.057: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.089: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.089: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.089: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.089: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.089: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.089: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.115: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.115: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.152: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.152: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.152: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.153: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.175: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.176: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.208: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.208: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.208: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.208: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.239: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.239: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.263: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.263: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.263: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.263: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.263: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.263: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.294: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.294: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.323: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.323: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.323: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.323: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.323: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.323: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.350: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.350: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.382: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.382: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.382: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.382: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.383: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.383: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.415: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.415: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.452: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.452: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.452: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.452: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.452: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.452: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.491: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.492: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.524: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.525: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.525: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.525: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.525: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.525: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.558: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.558: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.585: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.585: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.585: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.585: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.585: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.586: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.611: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.611: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.647: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.647: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.647: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.647: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.647: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.647: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.669: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.669: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.696: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.696: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.696: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.696: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.696: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.696: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.730: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.730: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.753: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.754: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.754: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.754: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.754: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.754: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.788: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.788: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.819: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.820: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.820: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.820: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.820: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.820: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.845: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.845: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.872: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.872: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.873: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.873: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.873: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.873: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.898: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.898: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.925: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.925: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.925: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.925: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.926: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.926: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:19.955: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.955: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.982: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:19.982: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:19.982: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:19.982: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:19.982: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:19.982: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.011: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.012: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.043: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.043: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.043: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.043: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.043: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.043: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.068: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.068: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.095: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.096: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.096: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.096: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.096: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.096: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.121: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.121: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.151: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.151: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.151: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.151: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.151: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.152: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.171: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.171: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.193: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.193: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.194: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.194: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.194: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.194: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.230: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.230: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.249: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.249: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.249: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.249: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.249: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.249: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.266: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.266: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.286: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.286: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.286: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.286: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.286: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.286: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.303: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.303: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.330: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.330: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.330: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.330: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.331: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.331: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.348: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.348: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.366: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.366: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.366: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.367: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.367: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.367: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.384: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.384: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.403: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.403: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.403: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.403: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.403: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.404: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.423: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.423: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.449: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.449: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.449: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.449: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.449: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.450: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.477: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.477: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.506: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.506: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.506: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.506: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.507: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.507: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.540: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.540: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.560: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.560: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.560: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.560: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.560: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.560: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.578: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.578: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.597: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.597: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.597: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.597: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.598: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.598: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.615: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.615: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.634: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.634: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.635: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.635: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.635: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.635: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.654: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.654: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.675: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.675: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.675: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.675: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.675: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.675: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.693: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.693: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.714: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.714: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.714: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.714: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.714: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.714: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.733: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.733: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.754: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.755: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.755: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.755: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.755: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.755: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.774: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.774: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.796: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.796: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.796: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.796: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.796: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.796: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.817: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.817: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.837: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.837: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.837: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.837: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.837: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.837: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.856: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.857: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.878: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.878: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.878: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.878: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.878: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.878: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.898: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.898: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.919: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.919: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.919: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.920: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.920: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.920: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.938: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.938: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.959: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.959: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.959: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.959: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.959: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.959: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:20.978: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.978: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.998: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:20.998: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:20.998: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:20.998: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:20.998: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:20.998: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.016: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.016: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.035: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.035: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.036: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.036: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.036: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.036: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.054: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.054: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.073: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.073: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.074: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.074: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.074: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.074: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.092: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.093: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.109: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.109: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.109: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.110: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:21.110: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.110: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:21.127: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.127: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:21.148: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:21.149: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.149: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:21.168: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.168: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:21.188: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:21.188: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.188: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:21.207: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.207: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:21.233: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.233: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.233: variance_after = 17
(process:17874): libfprint-SSM-DEBUG: 04:25:21.233: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.233: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.233: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.252: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.252: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.285: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.285: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.285: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.285: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.285: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.285: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.302: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.302: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.326: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.326: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.326: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.326: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.326: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.326: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.349: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.349: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.369: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.369: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.369: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.369: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.369: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.369: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.387: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.387: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.407: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.407: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.407: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.407: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.408: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.408: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.425: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.426: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.448: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.448: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.448: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.448: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.448: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.448: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.466: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.466: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.486: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.486: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.486: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.486: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.486: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.486: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.504: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.505: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.525: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.525: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.525: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.525: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.525: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.525: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.546: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.546: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.566: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.566: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.566: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.566: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.566: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.566: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.584: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.584: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.604: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.604: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.605: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.605: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.605: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.605: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.623: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.623: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.645: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.645: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.645: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.645: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.645: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.645: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.663: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.663: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.683: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.683: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.683: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.683: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.683: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.683: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.701: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.701: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.721: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.721: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.721: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.722: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.722: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.722: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.740: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.740: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.761: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.761: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.761: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.762: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.762: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.762: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.780: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.780: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.802: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.802: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.802: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.802: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.802: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.803: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.821: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.821: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.841: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.841: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.841: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.841: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.841: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.841: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.859: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.859: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.879: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.879: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.880: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.880: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.880: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.880: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.898: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.898: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.919: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.919: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.919: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.919: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.919: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.919: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.937: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.937: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.957: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.957: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.957: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.957: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.957: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.957: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:21.975: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.975: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.994: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:21.994: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:21.994: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:21.994: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:21.995: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:21.995: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.012: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.012: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.032: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.032: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.032: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.032: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.032: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.032: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.050: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.050: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.069: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.069: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.069: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.069: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.069: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.070: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.087: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.087: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.106: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.107: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.107: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.107: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.107: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.107: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.124: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.124: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.144: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.144: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.144: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.144: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.144: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.144: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.162: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.162: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.181: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.182: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.182: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.182: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.182: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.182: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.199: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.199: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.219: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.219: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.219: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.219: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.219: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.219: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.236: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.237: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.256: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.256: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.256: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.256: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.256: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.256: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.274: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.274: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.293: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.293: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.293: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.293: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.293: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.294: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.311: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.311: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.330: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.330: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.330: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.331: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.331: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.331: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.348: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.348: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.367: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.367: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.368: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.368: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.368: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.368: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.384: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.385: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.405: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.405: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.405: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.405: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.405: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.406: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.424: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.424: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.444: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.444: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.444: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.445: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.445: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.445: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.463: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.463: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.492: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.492: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.492: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.493: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.493: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.493: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.523: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.523: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.560: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.560: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.560: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.560: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.561: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.561: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.587: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.587: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.615: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.615: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.616: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.616: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.616: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.616: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.641: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.641: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.673: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.674: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.674: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.674: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.674: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.674: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.696: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.696: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.725: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.725: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.725: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.725: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.725: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.725: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.756: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.756: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.784: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.785: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.785: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.785: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.785: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.785: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.807: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.808: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.836: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.836: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.836: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.836: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.836: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.836: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.870: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.870: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.922: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.922: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.922: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.922: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.922: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.923: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.938: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.939: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.957: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.957: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.957: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.957: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.957: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.957: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:22.974: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.974: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.994: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:22.994: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:22.994: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:22.994: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:22.994: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:22.994: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.013: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.014: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.034: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.034: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.035: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.035: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.035: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.035: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.054: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.054: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.074: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.075: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.075: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.075: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.075: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.075: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.094: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.094: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.115: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.116: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.116: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.116: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.116: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.116: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.133: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.133: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.152: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.152: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.152: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.152: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.152: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.152: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.169: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.169: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.188: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.188: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.188: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.188: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.188: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.188: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.205: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.205: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.224: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.224: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.224: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.224: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.224: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.224: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.241: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.241: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.260: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.260: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.260: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.260: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.260: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.260: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.277: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.277: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.295: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.296: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.296: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.296: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.296: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.296: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.312: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.312: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.331: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.331: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.331: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.331: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.331: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.332: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.348: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.348: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.366: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.366: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.366: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.367: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.367: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.367: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.383: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.383: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.402: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.402: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.402: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.402: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.402: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.402: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.422: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.422: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.442: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.442: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.442: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.442: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.443: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.443: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.468: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.469: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.488: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.488: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.488: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.489: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.489: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.489: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.507: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.507: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.526: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.526: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.526: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.526: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.527: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.527: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.545: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.545: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.565: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.565: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.565: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.565: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.565: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.565: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.583: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.583: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.603: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.603: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.603: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.603: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.603: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.603: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.621: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.621: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.645: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.645: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.645: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.645: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:23.645: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.645: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:23.670: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.671: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:23.690: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:23.690: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.690: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:23.707: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.707: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:23.726: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:23.726: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.726: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:23.743: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.743: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:23.762: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.762: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.762: variance_after = 17
(process:17874): libfprint-SSM-DEBUG: 04:25:23.762: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.762: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.762: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.780: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.780: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.799: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.799: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.799: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.799: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.799: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.799: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.817: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.817: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.835: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.835: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.836: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.836: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.836: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.836: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.853: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.853: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.872: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.872: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.872: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.872: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.872: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.873: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.890: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.890: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.908: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.908: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.908: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.908: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.908: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.908: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.925: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.926: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.944: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.944: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.944: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.945: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.945: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.945: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.962: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.962: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.981: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:23.981: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:23.981: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:23.981: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:23.981: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.981: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:23.999: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:23.999: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.017: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.017: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.017: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.017: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.018: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.018: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.034: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.035: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.053: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.053: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.053: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.053: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.053: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.053: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.070: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.070: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.089: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.089: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.089: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.089: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.089: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.089: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.116: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.116: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.136: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.136: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.136: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.136: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.136: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.136: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.154: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.154: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.174: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.174: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.175: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.175: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.175: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.175: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.193: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.193: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.213: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.213: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.214: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.214: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.214: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.214: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.232: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.232: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.252: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.252: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.252: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.253: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.253: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.253: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.271: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.271: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.291: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.292: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.292: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.292: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.292: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.292: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.310: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.310: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.331: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.331: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.331: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.331: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.331: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.331: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.349: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.349: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.370: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.370: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.370: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.370: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.370: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.371: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.389: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.389: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.417: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.418: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.418: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.418: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.418: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.418: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.444: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.444: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.465: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.465: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.465: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.465: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.465: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.465: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.483: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.483: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.504: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.504: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.504: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.504: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.504: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.505: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.523: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.523: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.544: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.544: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.544: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.544: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.544: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.544: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.563: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.563: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.584: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.584: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.585: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.585: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.585: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.585: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.604: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.604: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.626: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.627: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.627: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.627: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.627: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.627: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.645: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.646: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.666: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.667: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.667: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.667: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.667: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.667: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.688: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.688: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.712: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.712: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.712: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.712: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.712: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.712: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.732: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.732: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.753: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.753: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.753: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.754: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.754: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.754: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.773: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.773: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.795: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.795: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.795: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.795: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.795: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.796: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.822: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.823: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.844: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.844: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.844: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.844: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.844: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.844: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.864: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.864: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.886: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.886: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.886: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.886: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.887: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.887: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.906: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.907: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.931: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.931: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.931: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.931: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.931: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.932: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.950: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.950: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.971: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:24.972: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:24.972: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:24.972: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:24.972: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.972: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:24.991: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:24.991: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.012: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.012: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.012: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.012: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.012: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.012: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.031: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.032: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.053: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.053: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.053: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.053: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.053: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.053: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.072: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.072: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.092: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.092: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.092: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.092: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.092: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.093: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.111: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.111: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.131: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.132: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.132: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.132: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.132: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.132: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.151: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.151: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.171: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.172: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.172: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.172: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.172: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.172: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.190: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.191: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.211: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.211: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.212: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.212: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.212: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.212: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.230: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.230: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.251: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.251: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.251: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.251: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.252: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.252: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.271: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.271: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.292: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.292: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.292: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.292: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.292: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.293: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.312: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.312: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.333: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.333: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.333: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.333: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.333: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.333: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.352: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.352: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.373: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.374: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.374: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.374: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.374: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.374: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.393: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.394: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.416: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.416: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.416: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.416: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.416: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.417: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.457: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.457: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.475: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.476: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.476: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.476: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.476: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.476: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.494: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.494: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.515: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.515: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.515: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.515: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.515: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.515: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.534: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.534: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.588: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.589: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.589: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.589: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.589: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.589: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.621: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.621: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.643: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.643: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.643: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.643: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.643: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.643: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.663: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.663: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.684: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.684: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.684: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.684: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.684: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.685: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.703: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.703: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.729: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.729: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.729: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.729: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.730: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.730: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.749: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.749: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.770: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.770: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.770: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.770: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.771: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.771: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.790: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.790: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.811: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.811: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.811: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.811: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.812: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.812: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.835: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.836: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.860: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.860: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.860: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.860: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.860: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.860: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.881: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.881: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.902: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.903: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.903: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.903: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.903: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.903: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.922: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.922: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.944: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.944: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.944: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.944: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.944: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.944: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:25.963: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.964: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.986: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:25.986: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:25.987: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:25.987: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:25.987: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:25.987: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.006: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.006: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.027: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.028: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.028: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.028: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.028: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.028: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.047: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.047: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.068: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.068: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.068: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.068: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.069: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.069: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.090: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.090: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.112: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.113: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.113: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.113: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.113: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.113: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.135: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.135: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.166: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.167: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.167: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.167: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.167: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.167: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.194: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.194: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.214: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.214: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.214: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.215: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.215: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.215: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.232: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.232: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.252: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.252: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.252: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.253: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.253: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.253: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.271: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.271: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.291: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.291: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.291: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.291: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.291: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.292: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.310: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.310: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.330: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.330: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.330: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.330: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.330: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.330: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.349: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.349: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.380: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.380: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.380: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.380: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.380: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.380: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.398: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.398: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.419: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.419: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.419: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.419: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.419: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.419: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.437: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.437: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.457: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.457: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.457: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.457: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.458: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.458: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.475: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.475: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.494: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.495: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.495: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.495: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.495: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.495: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.512: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.512: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.531: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.531: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.532: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.532: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.532: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.532: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.550: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.550: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.569: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.570: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.570: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.570: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.570: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.570: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.588: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.588: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.608: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.608: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.608: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.608: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.608: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.608: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.627: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.627: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.647: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.647: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.647: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.647: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.648: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.648: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.666: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.666: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.686: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.686: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.686: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.687: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.687: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.687: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.705: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.705: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.725: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.725: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.726: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.726: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.726: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.726: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.744: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.744: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.764: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.765: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.765: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.765: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.765: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.765: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.783: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.783: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.805: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.805: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.805: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.805: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.805: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.805: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.826: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.826: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.847: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.847: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.847: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.847: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.848: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.848: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.867: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.867: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.888: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.888: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.888: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.888: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.888: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.889: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.908: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.908: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.930: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.931: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.931: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.931: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.931: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.931: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.952: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.952: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.976: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:26.976: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:26.976: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:26.976: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:26.976: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.977: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:26.997: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:26.997: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.021: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.021: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.021: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.021: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.021: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.021: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.041: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.041: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.063: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.063: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.063: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.063: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.063: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.063: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.083: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.083: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.105: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.105: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.105: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.106: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.106: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.106: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.127: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.127: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.153: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.153: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.153: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.153: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.153: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.153: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.176: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.177: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.198: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.198: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.198: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.198: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.198: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.198: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.217: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.218: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.241: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.241: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.241: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.241: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.242: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.242: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.260: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.260: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.280: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.280: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.280: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.280: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.280: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.280: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.298: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.298: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.318: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.319: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.319: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.319: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.319: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.319: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.338: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.338: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.358: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.358: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.358: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.358: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.359: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.359: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.376: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.376: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.397: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.397: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.397: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.397: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.397: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.397: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.415: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.415: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.434: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.434: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.435: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.435: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.435: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.435: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.452: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.452: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.471: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.471: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.471: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.471: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.471: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.471: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.489: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.489: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.524: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.524: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.524: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.524: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.524: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.524: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.552: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.552: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.587: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.587: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.587: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.588: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.588: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.588: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.605: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.605: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.624: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.624: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.624: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.624: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.624: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.625: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.642: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.642: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.661: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.661: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.661: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.661: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.661: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.661: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.679: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.679: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.701: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.701: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.701: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.701: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.701: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.702: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.718: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.719: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.738: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.738: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.738: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.738: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.738: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.738: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.756: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.756: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.775: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.775: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.775: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.775: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.775: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.775: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.795: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.795: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.815: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.815: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.816: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.816: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.816: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.816: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.834: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.834: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.855: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.855: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.855: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.855: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.856: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.856: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.874: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.874: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.895: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.895: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.895: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.895: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.895: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.895: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.914: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.914: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.934: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.934: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.934: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.934: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.934: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.935: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.952: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.953: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.973: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:27.973: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:27.973: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:27.973: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:27.973: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.973: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:27.991: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:27.991: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.011: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.011: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.011: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.011: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.011: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.011: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.029: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.029: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.048: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.048: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.049: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.049: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.049: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.049: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.066: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.066: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.086: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.086: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.086: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.086: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.086: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.086: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.103: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.104: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.123: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.123: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.123: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.123: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.123: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.123: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.141: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.141: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.160: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.161: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.161: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.161: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.161: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.161: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.178: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.178: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.197: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.197: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.198: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.198: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.198: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.198: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.215: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.215: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.234: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.234: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.234: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.234: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.234: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.234: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.252: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.252: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.271: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.271: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.271: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.271: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.271: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.271: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.289: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.289: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.308: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.308: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.308: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.308: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.308: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.309: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.326: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.326: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.347: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.347: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.347: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.347: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.347: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.347: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.365: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.365: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.385: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.385: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.385: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.385: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.385: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.385: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.403: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.403: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.423: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.423: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.423: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.423: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.423: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.424: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.441: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.441: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.461: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.461: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.461: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.461: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.461: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.461: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.478: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.478: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.498: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.498: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.498: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.498: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.498: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.498: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.515: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.516: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.535: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.535: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.535: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.535: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.535: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.535: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.552: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.552: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.572: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.572: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.572: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.572: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.572: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.572: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.589: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.589: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.608: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.608: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.609: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.609: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.609: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.609: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.626: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.626: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.645: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.645: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.645: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.645: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.645: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.645: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.662: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.663: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.682: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.682: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.682: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.682: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.682: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.682: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.699: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.699: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.719: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.719: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.719: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.719: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.719: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.719: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.737: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.737: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.756: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.756: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.756: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.756: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.756: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.756: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.774: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.774: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.793: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.793: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.793: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.793: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.793: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.793: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.810: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.810: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.829: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.829: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.829: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.829: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.829: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.830: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.846: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.847: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.865: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.865: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.865: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.865: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.865: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.866: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.882: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.882: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.901: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.901: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.901: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.901: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.902: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.902: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.918: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.919: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.937: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.937: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.937: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.938: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.938: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.938: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.955: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.955: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.974: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:28.974: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:28.974: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:28.974: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:28.974: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.974: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:28.992: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:28.992: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.012: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.012: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.012: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.012: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.012: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.012: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.029: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.029: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.052: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.052: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.052: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.052: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.052: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.052: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.082: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.082: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.102: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.102: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.102: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.102: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.102: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.102: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.119: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.119: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.138: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.138: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.138: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.138: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.139: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.139: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.156: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.156: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.175: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.175: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.175: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.175: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.175: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.175: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.192: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.192: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.211: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.211: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.212: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.212: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.212: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.212: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.229: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.229: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.248: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.248: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.248: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.248: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.248: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.248: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.266: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.266: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.285: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.285: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.285: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.286: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.286: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.286: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.303: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.303: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.323: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.323: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.323: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.323: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.323: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.323: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.341: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.341: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.361: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.361: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.361: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.361: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.361: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.361: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.378: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.379: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.398: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.398: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.398: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.398: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.398: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.398: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.415: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.416: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.435: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.435: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.435: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.435: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.436: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.436: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.453: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.453: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.472: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.472: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.472: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.473: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.473: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.473: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.490: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.490: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.509: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.509: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.509: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.509: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.509: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.509: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.526: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.526: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.546: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.546: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.546: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.546: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.546: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.546: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.563: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.563: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.583: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.583: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.583: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.583: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.583: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.583: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.601: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.601: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.620: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.620: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.620: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.620: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.620: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.620: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.637: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.638: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.657: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.657: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.657: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.657: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.657: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.657: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.674: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.674: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.691: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.691: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.692: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.692: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:29.692: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.692: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:29.709: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.709: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:29.729: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:29.729: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.729: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:29.746: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.746: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:29.766: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:29.766: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.766: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:29.783: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.783: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:29.802: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.802: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.803: variance_after = 20
(process:17874): libfprint-SSM-DEBUG: 04:25:29.803: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.803: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.803: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.820: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.820: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.839: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.839: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.839: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.840: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.840: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.840: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.857: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.857: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.876: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.876: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.876: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.876: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.876: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.876: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.894: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.894: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.913: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.914: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.914: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.914: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.914: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.914: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.931: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.931: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.951: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.951: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.951: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.951: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.951: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.951: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:29.969: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.969: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.989: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:29.989: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:29.989: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:29.990: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:29.990: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:29.990: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.007: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.007: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.026: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.027: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.027: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.027: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.027: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.027: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.044: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.045: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.064: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.064: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.064: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.065: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.065: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.065: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.082: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.082: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.102: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.102: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.102: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.102: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.102: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.102: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.120: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.120: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.139: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.139: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.140: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.140: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.140: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.140: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.157: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.157: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.176: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.177: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.177: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.177: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.177: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.177: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.194: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.194: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.213: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.213: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.213: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.213: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.213: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.213: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.230: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.230: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.249: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.249: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.249: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.250: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.250: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.250: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.267: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.267: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.286: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.286: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.286: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.287: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.287: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.287: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.304: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.304: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.323: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.324: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.324: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.324: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.324: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.324: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.341: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.341: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.360: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.361: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.361: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.361: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.361: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.361: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.378: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.379: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.399: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.399: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.399: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.399: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.399: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.399: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.416: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.416: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.435: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.436: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.436: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.436: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.436: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.436: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.454: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.454: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.473: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.473: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.473: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.473: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.473: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.473: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.490: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.490: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.509: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.509: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.509: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.509: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.509: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.510: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.526: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.527: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.546: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.546: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.546: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.546: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.546: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.546: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.563: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.563: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.582: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.582: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.582: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.582: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.582: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.582: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.600: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.600: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.619: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.619: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.619: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.619: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.620: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.620: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.637: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.637: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.657: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.657: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.657: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.657: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.657: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.657: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.675: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.675: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.695: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.695: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.695: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.695: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.695: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.695: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.713: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.713: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.733: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.734: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.734: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.734: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.734: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.734: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.751: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.752: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.771: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.771: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.771: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.771: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.771: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.771: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.789: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.789: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.808: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.808: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.808: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.808: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.808: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.808: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.826: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.826: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.845: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.846: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.846: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.846: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.846: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.846: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.863: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.863: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.883: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.883: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.883: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.883: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.883: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.883: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.901: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.901: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.920: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.920: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.920: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.920: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.921: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.921: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.938: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.938: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.957: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.957: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.957: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.958: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.958: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.958: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:30.975: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.975: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.994: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:30.994: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:30.995: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:30.995: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:30.995: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:30.995: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.012: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.012: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.032: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.032: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.032: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.032: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.032: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.032: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.050: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.050: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.069: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.069: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.069: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.069: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.069: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.069: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.086: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.086: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.106: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.106: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.106: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.106: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.106: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.106: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.123: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.123: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.142: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.142: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.142: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.143: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.143: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.143: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.160: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.160: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.179: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.180: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.180: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.180: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.180: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.180: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.197: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.197: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.216: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.217: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.217: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.217: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.217: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.217: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.234: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.234: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.253: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.253: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.253: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.253: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.254: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.254: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.271: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.271: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.290: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.290: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.291: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.291: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.291: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.291: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.308: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.308: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.328: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.328: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.328: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.328: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.328: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.328: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.345: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.346: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.365: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.365: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.365: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.365: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.365: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.365: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.383: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.383: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.403: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.403: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.403: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.403: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.403: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.403: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.421: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.421: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.442: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.442: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.442: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.442: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.442: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.442: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.460: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.460: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.480: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.480: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.480: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.480: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.480: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.480: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.497: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.498: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.517: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.517: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.517: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.517: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.517: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.517: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.535: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.535: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.554: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.554: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.554: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.554: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.554: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.554: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.571: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.571: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.590: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.591: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.591: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.591: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.591: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.591: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.608: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.608: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.627: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.627: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.627: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.627: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.628: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.628: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.644: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.644: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.663: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.663: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.663: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.664: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.664: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.664: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.681: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.681: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.700: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.701: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.701: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.701: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.701: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.701: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.718: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.718: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.737: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.738: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.738: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.738: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.738: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.738: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.755: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.755: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.774: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.774: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.774: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.774: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.774: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.774: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.791: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.791: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.810: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.810: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.810: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.810: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.810: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.810: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.827: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.827: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.846: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.847: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.847: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.847: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.847: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.847: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.864: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.864: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.883: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.883: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.883: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.884: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.884: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.884: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.901: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.901: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.920: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.920: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.920: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.921: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.921: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.921: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.938: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.938: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.957: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.957: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.957: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.957: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.958: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.958: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:31.975: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.975: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.994: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:31.994: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:31.994: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:31.995: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:31.995: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:31.995: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.012: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.012: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.031: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.032: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.032: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.032: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.032: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.032: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.049: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.049: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.069: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.069: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.069: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.069: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.069: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.069: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.087: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.087: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.106: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.106: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.106: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.107: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.107: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.107: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.124: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.124: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.144: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.144: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.144: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.144: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.144: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.144: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.161: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.161: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.180: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.180: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.180: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.180: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.180: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.180: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.198: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.198: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.217: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.217: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.217: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.217: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.217: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.217: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.235: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.235: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.254: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.254: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.255: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.255: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.255: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.255: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.272: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.272: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.291: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.291: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.291: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.291: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.292: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.292: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.309: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.309: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.328: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.328: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.328: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.328: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.328: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.328: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.346: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.346: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.365: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.365: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.365: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.366: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.366: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.366: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.383: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.384: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.403: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.403: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.403: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.403: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.403: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.403: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.421: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.421: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.440: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.440: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.440: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.440: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.440: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.441: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.458: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.458: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.478: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.478: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.478: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.478: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.478: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.478: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.496: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.496: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.515: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.515: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.515: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.515: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.515: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.515: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.533: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.533: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.553: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.553: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.554: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.554: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.554: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.554: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.571: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.571: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.589: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.589: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.589: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.589: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:32.589: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.589: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:32.607: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.607: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:32.627: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:32.628: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.628: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:32.645: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.645: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:32.664: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:32.665: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.665: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:32.682: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.682: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:32.701: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.702: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.702: variance_after = 17
(process:17874): libfprint-SSM-DEBUG: 04:25:32.702: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.702: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.702: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.719: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.719: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.738: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.738: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.738: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.738: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.738: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.739: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.756: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.756: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.776: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.776: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.776: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.776: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.776: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.776: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.793: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.794: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.813: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.813: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.813: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.813: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.813: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.814: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.831: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.831: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.850: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.850: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.850: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.850: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.850: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.850: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.867: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.868: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.887: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.887: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.887: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.887: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.887: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.887: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.904: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.905: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.924: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.924: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.924: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.924: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.925: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.925: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.942: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.942: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.964: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:32.964: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:32.965: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:32.965: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:32.965: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.965: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:32.982: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:32.982: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.001: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.001: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.002: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.002: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.002: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.002: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.019: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.019: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.038: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.038: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.038: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.038: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.038: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.038: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.056: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.056: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.076: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.076: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.076: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.076: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.076: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.076: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.093: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.093: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.112: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.113: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.113: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.113: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.113: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.113: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.130: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.130: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.149: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.150: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.150: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.150: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.150: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.150: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.167: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.167: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.187: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.187: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.187: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.187: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.188: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.188: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.205: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.205: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.224: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.224: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.225: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.225: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.225: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.225: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.242: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.242: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.261: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.261: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.261: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.261: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.261: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.261: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.278: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.279: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.298: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.298: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.298: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.298: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.298: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.298: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.315: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.315: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.334: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.335: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.335: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.335: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.335: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.335: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.352: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.352: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.371: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.371: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.371: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.372: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.372: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.372: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.389: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.389: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.408: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.408: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.408: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.409: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.409: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.409: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.426: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.426: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.446: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.446: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.446: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.446: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.446: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.446: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.463: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.463: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.483: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.483: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.483: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.483: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.484: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.484: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.501: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.501: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.521: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.521: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.521: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.521: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.521: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.521: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.539: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.539: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.559: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.559: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.559: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.559: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.559: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.559: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.576: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.577: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.596: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.596: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.596: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.596: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.596: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.596: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.614: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.614: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.633: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.634: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.634: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.634: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.634: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.634: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.652: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.652: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.672: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.672: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.672: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.672: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.672: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.672: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.690: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.690: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.709: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.709: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.710: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.710: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.710: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.710: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.728: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.728: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.749: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.749: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.749: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.749: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.749: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.749: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.767: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.767: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.787: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.787: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.787: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.787: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.787: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.787: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.804: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.804: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.824: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.825: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.825: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.825: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.825: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.825: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.843: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.843: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.862: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.862: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.862: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.862: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.862: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.863: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.880: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.880: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.899: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.900: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.900: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.900: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.900: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.900: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.917: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.917: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.937: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.937: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.937: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.937: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.937: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.937: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.955: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.955: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.975: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:33.975: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:33.975: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:33.975: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:33.975: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.975: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:33.993: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:33.993: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.012: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.013: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.013: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.013: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.013: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.013: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.030: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.030: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.050: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.050: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.050: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.050: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.050: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.050: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.067: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.068: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.087: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.087: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.087: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.087: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.087: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.088: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.105: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.105: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.124: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.124: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.124: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.124: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.124: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.125: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.142: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.142: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.162: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.162: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.162: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.162: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.162: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.162: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.180: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.180: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.200: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.200: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.200: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.200: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.200: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.200: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.218: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.218: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.238: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.238: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.238: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.238: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.238: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.238: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.255: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.255: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.274: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.275: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.275: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.275: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.275: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.275: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.292: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.292: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.311: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.312: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.312: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.312: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.312: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.312: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.329: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.329: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.348: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.348: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.348: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.348: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.349: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.349: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.366: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.366: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.385: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.385: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.385: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.385: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.385: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.385: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.402: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.403: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.422: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.422: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.422: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.422: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.422: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.422: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.440: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.440: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.460: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.460: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.460: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.460: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.460: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.460: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.477: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.477: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.496: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.497: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.497: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.497: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.497: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.497: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.514: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.514: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.531: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.531: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.532: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.532: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:34.532: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.532: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:34.549: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.549: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:34.568: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:34.568: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.569: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:34.585: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.586: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:34.605: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:34.605: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.605: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:34.622: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.622: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:34.641: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.641: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.642: variance_after = 17
(process:17874): libfprint-SSM-DEBUG: 04:25:34.642: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.642: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.642: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.659: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.659: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.679: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.679: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.679: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.679: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.679: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.680: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.697: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.697: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.717: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.717: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.717: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.717: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.717: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.717: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.734: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.734: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.754: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.754: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.754: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.754: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.754: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.754: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.771: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.771: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.791: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.791: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.791: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.791: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.791: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.791: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.808: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.809: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.827: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.828: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.828: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.828: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.828: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.828: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.845: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.845: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.865: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.865: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.865: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.865: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.865: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.865: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.882: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.882: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.902: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.902: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.902: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.902: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.902: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.902: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.919: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.919: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.938: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.938: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.938: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.938: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.938: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.938: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.955: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.955: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.974: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:34.975: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:34.975: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:34.975: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:34.975: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.975: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:34.992: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:34.992: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.012: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.013: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.013: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.013: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.013: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.013: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.031: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.031: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.050: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.050: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.050: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.050: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.050: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.051: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.120: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.120: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.161: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.162: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.162: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.162: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.162: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.162: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.179: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.179: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.198: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.198: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.198: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.199: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.199: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.199: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.216: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.216: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.235: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.235: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.235: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.235: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.236: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.236: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.254: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.254: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.273: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.273: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.273: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.273: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.274: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.274: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.291: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.291: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.310: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.310: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.310: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.310: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.310: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.310: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.327: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.327: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.347: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.347: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.347: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.347: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.347: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.347: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.364: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.364: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.383: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.384: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.384: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.384: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.384: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.384: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.401: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.401: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.420: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.420: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.420: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.420: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.420: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.420: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.437: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.438: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.457: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.458: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.458: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.458: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.458: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.458: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.475: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.475: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.495: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.495: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.495: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.496: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.496: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.496: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.513: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.513: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.533: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.533: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.533: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.534: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.534: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.534: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.552: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.552: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.572: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.572: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.572: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.572: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.573: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.573: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.591: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.591: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.611: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.611: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.611: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.611: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.612: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.612: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.630: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.630: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.650: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.650: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.650: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.650: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.650: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.650: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.669: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.669: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.688: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.688: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.688: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.688: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.688: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.689: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.706: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.706: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.726: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.726: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.726: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.726: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.726: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.726: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.743: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.744: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.763: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.763: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.763: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.763: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.763: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.764: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.781: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.781: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.800: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.800: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.800: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.801: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.801: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.801: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.817: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.818: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.837: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.837: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.837: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.837: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.837: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.837: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.855: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.855: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.875: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.875: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.875: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.875: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.875: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.876: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.893: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.893: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.914: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.914: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.914: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.914: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.914: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.914: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.932: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.932: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.951: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.951: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.951: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.952: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.952: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.952: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:35.969: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.969: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.989: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:35.989: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:35.989: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:35.989: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:35.989: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:35.989: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.006: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.006: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.025: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.025: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.025: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.026: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.026: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.026: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.043: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.043: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.062: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.062: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.063: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.063: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.063: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.063: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.080: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.080: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.100: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.100: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.100: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.100: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.100: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.100: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.117: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.117: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.137: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.137: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.137: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.137: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.137: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.137: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.154: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.154: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.174: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.174: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.174: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.174: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.174: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.174: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.191: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.191: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.211: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.211: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.211: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.211: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.211: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.211: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.228: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.228: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.247: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.247: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.247: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.247: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.248: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.248: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.265: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.265: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.283: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.284: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.284: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.284: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.284: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.284: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.301: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.301: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.320: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.320: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.320: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.321: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.321: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.321: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.338: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.338: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.357: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.357: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.357: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.357: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.357: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.357: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.375: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.375: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.394: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.394: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.394: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.394: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.394: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.394: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.411: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.411: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.428: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.429: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.429: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.429: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:36.429: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.429: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:36.446: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.446: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:36.466: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:36.466: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.466: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:36.483: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.483: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:36.503: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:36.503: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.503: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:36.520: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.520: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:36.539: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.540: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.540: variance_after = 17
(process:17874): libfprint-SSM-DEBUG: 04:25:36.540: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.540: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.540: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.557: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.557: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.577: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.577: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.577: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.577: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.577: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.577: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.594: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.594: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.613: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.614: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.614: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.614: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.614: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.614: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.631: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.631: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.651: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.651: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.651: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.651: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.651: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.651: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.669: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.669: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.688: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.688: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.688: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.688: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.688: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.688: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.705: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.706: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.725: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.725: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.725: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.725: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.725: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.725: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.742: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.742: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.761: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.762: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.762: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.762: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.762: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.762: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.779: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.779: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.798: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.798: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.798: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.798: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.799: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.799: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.815: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.816: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.835: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.835: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.835: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.835: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.835: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.835: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.852: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.852: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.872: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.872: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.872: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.872: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.872: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.872: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.889: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.890: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.909: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.909: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.909: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.909: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.909: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.909: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.926: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.926: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.945: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.945: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.945: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.945: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.946: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.946: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:36.963: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.963: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.982: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:36.982: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:36.982: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:36.983: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:36.983: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:36.983: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.000: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.000: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.019: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.019: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.019: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.019: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.019: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.020: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.037: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.037: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.056: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.056: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.056: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.056: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.056: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.056: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.073: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.073: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.092: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.092: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.092: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.092: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.092: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.093: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.109: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.109: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.129: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.129: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.129: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.129: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.129: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.129: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.146: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.146: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.165: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.165: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.165: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.165: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.166: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.166: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.182: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.183: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.202: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.202: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.202: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.202: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.202: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.202: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.219: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.219: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.239: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.239: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.239: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.239: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.239: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.239: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.256: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.256: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.275: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.275: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.275: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.275: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.275: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.276: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.292: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.293: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.312: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.312: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.312: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.312: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.312: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.312: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.329: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.329: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.348: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.348: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.348: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.348: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.348: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.348: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.365: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.365: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.384: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.384: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.384: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.384: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.384: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.384: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.402: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.402: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.421: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.421: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.421: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.421: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.421: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.421: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.438: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.438: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.457: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.457: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.457: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.457: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.458: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.458: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.474: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.474: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.493: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.493: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.493: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.493: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.494: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.494: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.510: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.511: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.529: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.529: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.530: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.530: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.530: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.530: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.546: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.546: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.565: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.565: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.565: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.565: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.565: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.565: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.582: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.582: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.601: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.601: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.601: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.601: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.601: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.602: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.618: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.618: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.637: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.637: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.637: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.637: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.637: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.637: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.654: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.654: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.673: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.673: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.673: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.673: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.673: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.673: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.690: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.690: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.709: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.709: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.709: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.709: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.709: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.709: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.725: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.726: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.744: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.744: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.745: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.745: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.745: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.745: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.761: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.761: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.780: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.780: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.780: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.781: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.781: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.781: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.798: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.798: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.817: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.817: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.817: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.817: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.817: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.817: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.834: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.834: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.853: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.853: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.854: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.854: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.854: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.854: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.871: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.871: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.890: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.890: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.890: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.890: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.890: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.890: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.907: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.907: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.926: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.926: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.926: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.926: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.926: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.926: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.943: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.943: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.962: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.963: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.963: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.963: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.963: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.963: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:37.980: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.980: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.998: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:37.999: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:37.999: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:37.999: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:37.999: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:37.999: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.016: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.016: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.033: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.033: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.033: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.033: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:38.033: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.033: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:38.050: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.050: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:38.072: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:38.072: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.072: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:38.089: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.089: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:38.108: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:38.108: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.108: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:38.125: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.125: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:38.144: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.144: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.145: variance_after = 17
(process:17874): libfprint-SSM-DEBUG: 04:25:38.145: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.145: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.145: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.162: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.162: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.181: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.181: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.181: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.181: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.181: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.181: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.198: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.198: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.217: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.217: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.217: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.218: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.218: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.218: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.235: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.235: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.254: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.254: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.254: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.254: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.254: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.254: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.271: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.271: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.290: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.290: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.290: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.290: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.291: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.291: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.308: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.308: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.326: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.327: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.327: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.327: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.327: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.327: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.344: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.344: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.364: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.364: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.364: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.364: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.364: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.364: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.381: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.381: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.400: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.400: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.400: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.400: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.400: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.400: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.417: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.418: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.436: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.436: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.436: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.436: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.437: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.437: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.454: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.454: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.473: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.473: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.473: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.473: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.473: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.473: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.490: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.490: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.509: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.509: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.509: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.510: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.510: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.510: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.527: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.527: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.546: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.546: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.546: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.546: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.547: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.547: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.564: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.564: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.583: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.583: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.583: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.583: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.583: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.583: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.600: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.600: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.619: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.619: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.619: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.619: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.620: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.620: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.637: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.637: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.656: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.656: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.656: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.656: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.656: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.656: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.673: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.673: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.692: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.692: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.692: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.692: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.693: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.693: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.710: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.710: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.729: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.729: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.729: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.729: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.729: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.729: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.746: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.746: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.765: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.766: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.766: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.766: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.766: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.766: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.783: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.783: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.802: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.802: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.802: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.802: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.802: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.802: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.819: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.820: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.839: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.839: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.839: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.839: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.839: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.839: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.856: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.856: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.875: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.875: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.876: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.876: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.876: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.876: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.893: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.893: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.911: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.912: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.912: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.912: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.912: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.912: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.929: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.929: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.948: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.948: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.948: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.949: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.949: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.949: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:38.966: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.966: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.985: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:38.985: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:38.985: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:38.985: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:38.985: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:38.985: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.002: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.002: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.021: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.022: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.022: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.022: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.022: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.022: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.039: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.039: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.058: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.058: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.058: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.058: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.058: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.059: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.076: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.076: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.095: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.095: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.095: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.095: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.095: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.095: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.112: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.112: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.131: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.131: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.131: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.132: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.132: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.132: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.149: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.149: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.168: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.168: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.168: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.168: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.168: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.168: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.186: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.186: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.205: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.205: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.205: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.205: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.205: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.205: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.222: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.222: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.241: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.242: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.242: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.242: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.242: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.242: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.259: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.259: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.278: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.278: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.278: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.278: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.278: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.278: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.295: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.295: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.315: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.315: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.315: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.315: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.315: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.315: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.334: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.334: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.353: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.353: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.353: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.353: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.353: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.353: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.370: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.370: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.390: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.390: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.390: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.390: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.390: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.390: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.407: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.407: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.427: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.427: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.427: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.427: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.427: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.427: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.444: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.445: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.464: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.464: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.464: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.464: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.464: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.464: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.482: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.482: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.501: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.501: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.501: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.501: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.502: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.502: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.518: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.519: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.540: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.541: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.541: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.541: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.541: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.541: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.556: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.556: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.578: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.578: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.578: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.578: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.578: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.578: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.594: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.594: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.612: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.613: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.613: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.613: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.613: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.613: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.630: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.630: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.648: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.649: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.649: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.649: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.649: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.649: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.666: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.666: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.684: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.684: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.684: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.684: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.685: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.685: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.702: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.702: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.721: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.721: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.721: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.721: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.721: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.721: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.739: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.739: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.758: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.758: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.759: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.759: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.759: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.759: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.776: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.776: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.793: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.793: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.793: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.793: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:39.793: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.793: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:39.810: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.810: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:39.830: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:39.830: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.830: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:39.847: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.847: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:39.866: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:39.866: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.866: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:39.883: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.883: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:39.902: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.902: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.903: variance_after = 16
(process:17874): libfprint-SSM-DEBUG: 04:25:39.903: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.903: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.903: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.920: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.920: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.939: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.939: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.939: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.939: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.939: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.940: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.956: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.957: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.976: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:39.976: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:39.976: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:39.976: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:39.976: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.976: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:39.993: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:39.993: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.012: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.012: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.012: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.012: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.013: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.013: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.029: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.030: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.048: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.049: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.049: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.049: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.049: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.049: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.066: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.066: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.085: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.085: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.085: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.085: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.085: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.085: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.102: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.103: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.121: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.122: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.122: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.122: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.122: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.122: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.139: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.139: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.158: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.158: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.158: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.158: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.158: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.158: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.175: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.175: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.194: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.194: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.194: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.194: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.194: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.194: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.211: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.211: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.230: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.230: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.230: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.230: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.230: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.231: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.247: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.247: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.266: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.267: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.267: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.267: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.267: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.267: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.284: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.284: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.303: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.303: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.303: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.303: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.303: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.303: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.320: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.320: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.339: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.339: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.339: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.339: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.339: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.339: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.356: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.356: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.375: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.376: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.376: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.376: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.376: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.376: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.393: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.393: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.412: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.412: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.412: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.412: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.412: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.412: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.429: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.429: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.448: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.448: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.448: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.448: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.448: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.448: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.465: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.465: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.484: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.484: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.484: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.484: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.484: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.485: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.501: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.502: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.520: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.521: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.521: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.521: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.521: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.521: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.538: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.538: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.557: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.557: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.557: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.557: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.557: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.557: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.574: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.574: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.593: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.593: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.593: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.593: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.593: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.593: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.610: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.610: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.629: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.629: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.629: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.629: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.629: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.630: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.646: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.647: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.665: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.666: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.666: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.666: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.666: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.666: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.683: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.683: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.702: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.702: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.702: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.702: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.702: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.702: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.719: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.719: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.738: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.738: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.738: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.738: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.738: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.738: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.755: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.755: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.774: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.774: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.775: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.775: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.775: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.775: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.792: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.792: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.811: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.811: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.811: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.811: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.811: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.811: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.828: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.828: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.847: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.847: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.847: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.847: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.847: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.847: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.864: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.865: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.883: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.883: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.884: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.884: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.884: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.884: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.901: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.901: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.920: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.920: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.920: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.920: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.920: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.920: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.937: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.937: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.956: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.956: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.956: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.956: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.956: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.956: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:40.973: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.973: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.992: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:40.992: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:40.992: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:40.992: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:40.992: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:40.992: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.009: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.009: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.028: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.028: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.028: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.029: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.029: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.029: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.046: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.046: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.064: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.065: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.065: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.065: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.065: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.065: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.082: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.082: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.100: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.101: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.101: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.101: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.101: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.101: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.118: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.118: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.137: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.137: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.137: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.137: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.137: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.137: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.154: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.154: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.173: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.173: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.173: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.173: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.173: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.173: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.190: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.190: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.209: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.209: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.209: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.210: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.210: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.210: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.227: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.227: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.246: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.246: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.246: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.246: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.246: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.246: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.263: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.263: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.282: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.282: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.282: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.282: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.282: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.282: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.299: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.299: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.317: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.318: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.318: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.318: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.318: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.318: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.335: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.335: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.353: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.353: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.354: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.354: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.354: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.354: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.370: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.370: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.389: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.389: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.389: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.389: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.390: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.390: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.406: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.406: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.425: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.425: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.425: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.425: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.425: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.425: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.442: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.442: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.461: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.461: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.461: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.461: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.461: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.461: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.478: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.478: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.495: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.495: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.495: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.495: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:41.495: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.495: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:41.512: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.512: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:41.530: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:41.531: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.531: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:41.548: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.548: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:41.566: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:41.567: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.567: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:41.583: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.584: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:41.602: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.602: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.603: variance_after = 17
(process:17874): libfprint-SSM-DEBUG: 04:25:41.603: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.603: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.603: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.619: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.619: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.638: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.638: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.638: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.638: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.638: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.638: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.655: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.655: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.674: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.674: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.674: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.674: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.674: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.674: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.691: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.691: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.710: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.710: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.710: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.710: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.710: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.710: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.727: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.727: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.746: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.746: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.746: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.746: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.746: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.746: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.763: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.763: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.781: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.782: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.782: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.782: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.782: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.782: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.799: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.799: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.817: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.818: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.818: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.818: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.818: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.818: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.835: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.835: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.853: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.853: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.853: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.854: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.854: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.854: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.870: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.871: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.890: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.890: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.890: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.890: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.890: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.890: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.907: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.907: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.926: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.926: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.926: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.926: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.926: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.926: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.943: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.943: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.962: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.962: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.962: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.962: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.962: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.963: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:41.979: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.979: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.998: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:41.998: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:41.998: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:41.998: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:41.998: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:41.998: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.015: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.015: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.034: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.034: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.034: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.034: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.034: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.034: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.051: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.051: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.069: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.069: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.069: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.069: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.070: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.070: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.086: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.086: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.105: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.105: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.105: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.105: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.105: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.105: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.122: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.122: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.140: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.141: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.141: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.141: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.141: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.141: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.158: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.158: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.176: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.176: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.176: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.176: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.176: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.176: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.193: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.193: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.212: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.212: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.212: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.212: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.212: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.212: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.229: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.229: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.247: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.248: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.248: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.248: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.248: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.248: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.265: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.265: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.283: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.284: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.284: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.284: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.284: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.284: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.301: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.301: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.319: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.320: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.320: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.320: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.320: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.320: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.337: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.337: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.355: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.355: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.356: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.356: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.356: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.356: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.372: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.373: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.391: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.391: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.392: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.392: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.392: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.392: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.409: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.409: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.428: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.428: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.428: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.428: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.428: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.428: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.445: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.445: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.464: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.464: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.464: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.464: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.464: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.464: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.481: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.482: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.500: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.501: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.501: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.501: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.501: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.501: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.518: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.518: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.537: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.537: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.537: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.537: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.537: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.537: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.554: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.554: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.573: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.573: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.573: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.573: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.573: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.574: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.590: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.590: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.609: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.609: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.610: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.610: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.610: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.610: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.627: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.627: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.646: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.646: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.646: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.646: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.646: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.646: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.663: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.663: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.682: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.682: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.682: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.682: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.682: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.682: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.699: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.699: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.718: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.719: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.719: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.719: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.719: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.719: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.736: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.736: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.754: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.755: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.755: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.755: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.755: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.755: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.772: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.772: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.791: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.791: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.791: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.791: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.791: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.791: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.807: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.808: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.826: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.826: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.827: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.827: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.827: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.827: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.843: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.844: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.862: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.862: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.862: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.863: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.863: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.863: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.879: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.880: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.898: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.899: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.899: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.899: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.899: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.899: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.916: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.916: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.934: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.934: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.935: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.935: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.935: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.935: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.951: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.952: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.971: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:42.971: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:42.971: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:42.971: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:42.971: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.971: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:42.988: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:42.988: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.007: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:43.007: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.007: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:43.007: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:43.007: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.007: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:43.024: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.025: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.043: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:43.044: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.044: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:43.044: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:43.044: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.044: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:43.061: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.061: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.079: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:43.079: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.079: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:43.079: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:43.079: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.079: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:43.096: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.096: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:43.116: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:43.116: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.116: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:43.133: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.133: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:43.152: [vfs7552] CAPTURE_NUM_STATES entering state 2
(process:17874): libfprint-SSM-DEBUG: 04:25:43.152: [vfs7552] REQUEST CHUNK entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.153: Sending vfs7552_read_image_chunk
(process:17874): libfprint-SSM-DEBUG: 04:25:43.169: [vfs7552] REQUEST CHUNK completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.170: [vfs7552] CAPTURE_NUM_STATES entering state 3
(process:17874): libfprint-SSM-DEBUG: 04:25:43.188: [vfs7552] CAPTURE_NUM_STATES entering state 4
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.188: Cleaning image
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.189: variance_after = 16
(process:17874): libfprint-SSM-DEBUG: 04:25:43.189: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:43.189: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.189: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:43.206: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.206: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.225: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:43.225: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.225: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:43.225: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:43.225: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.225: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:43.242: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.243: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.261: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:43.261: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.262: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:43.262: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:43.262: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.262: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:43.279: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.279: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.297: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:43.298: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.298: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:43.298: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:43.298: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.298: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:43.314: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.314: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.333: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:43.333: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.333: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:43.333: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:43.333: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.333: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:43.350: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.350: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.368: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:43.369: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.369: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:43.369: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:43.369: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.369: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:43.385: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.385: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.404: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:43.404: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.404: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:43.404: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:43.404: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.404: Sending vfs7552_is_image_ready
(process:17874): libfprint-SSM-DEBUG: 04:25:43.421: [vfs7552] QUERY DATA READY entering state 1
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.421: Receiving 64 bytes
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.439: Got 6 bytes out of 64
(process:17874): libfprint-SSM-DEBUG: 04:25:43.439: [vfs7552] QUERY DATA READY completed successfully
(process:17874): libfprint-SSM-DEBUG: 04:25:43.439: [vfs7552] CAPTURE_NUM_STATES entering state 1
(process:17874): libfprint-SSM-DEBUG: 04:25:43.439: [vfs7552] CAPTURE_NUM_STATES entering state 0
(process:17874): libfprint-SSM-DEBUG: 04:25:43.439: [vfs7552] QUERY DATA READY entering state 0
(process:17874): libfprint-vfs7552-DEBUG: 04:25:43.439: Sending vfs7552_is_image_ready
** (umockdev-run:17871): DEBUG: 04:25:43.445: umockdev-utils.vala:50: umockdev: caught signal 15, propagating to child
** (umockdev-run:17871): DEBUG: 04:25:43.448: umockdev.vala:150: Removing test bed /tmp/umockdev.P88QB2
----------------------------------- stderr -----------------------------------
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
libusb: error [op_handle_events] cannot find handle for fd 9
** (umockdev-run:17871): WARNING **: 04:25:43.450: umockdev-ioctl.vala:926: Error resolving IOCtl data: Error receiving data: Connection reset by peer
==============================================================================
Summary of Failures:
108/116 libfprint:drivers / aes2501 TIMEOUT 75.08s killed by signal 15 SIGTERM
112/116 libfprint:drivers / elanspi TIMEOUT 75.10s killed by signal 15 SIGTERM
116/116 libfprint:drivers / vfs7552 TIMEOUT 75.54s killed by signal 15 SIGTERM
Ok: 113
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 0
Timeout: 3
dh_auto_test: error: cd obj-arm-linux-gnueabihf && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test -C /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf --timeout-multiplier 5 returned exit code 3
make[1]: *** [debian/rules:22: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:16: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2
--------------------------------------------------------------------------------
Build finished at 2023-09-16T04:25:47Z
Finished
--------
+------------------------------------------------------------------------------+
| Cleanup |
+------------------------------------------------------------------------------+
Purging /<<BUILDDIR>>
Not cleaning session: cloned chroot in use
E: Build failure (dpkg-buildpackage died)
+------------------------------------------------------------------------------+
| Summary |
+------------------------------------------------------------------------------+
Build Architecture: armhf
Build-Space: 57400
Build-Time: 216
Distribution: trixie-staging
Fail-Stage: build
Host Architecture: armhf
Install-Time: 531
Job: libfprint_1:1.94.6-2
Machine Architecture: armhf
Package: libfprint
Package-Time: 777
Source-Version: 1:1.94.6-2
Space: 57400
Status: attempted
Version: 1:1.94.6-2
--------------------------------------------------------------------------------
Finished at 2023-09-16T04:25:47Z
Build needed 00:12:57, 57400k disk space